WG: Re: API calls

This message is in MIME format.

--=_37shrcfs4h0k
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable



----- Weitergeleitete Nachricht von [email protected] -----
      Datum: Fri,  2 Feb 2007 09:53:51 -0600
        Von: Nathan Mills <[email protected]>
    Betreff: Re: [whups] API calls
         An: Jan Schneider <[email protected]>

Quoting Jan Schneider <[email protected]>:

> Zitat von Nathan Mills <[email protected]>:
>
>> Is there a particular reason that the show method only has a link   =20
>> parameter, rather than being fully implemented like the rest? It
>
> Yes, because that's the purpose of the "show" api methods.

Maybe I'm just being unobservant, but what's the recommended way to =20
get info about one particular ticket? One can use =20
get_assigned_ticket_ids to get an array of ticket IDs assigned to the =20
particular user, but what then? The (seemingly) inaptly named =20
getTicketDetails API call takes a queue and returns all the tickets in =20
the queue.

-Nathan




----- Ende der weitergeleiteten Nachricht -----


Jan.

--=20
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
--=_37shrcfs4h0k
Content-Type: message/rfc822;
	name="Weitergeleitete Nachricht: Re: [whups] API calls"
MIME-Version: 1.0

Return-Path: <[email protected]>
Received: from neo.wg.de ([unix socket]) by neo (Cyrus v2.2.13) with LMTPA;
	Fri, 02 Feb 2007 17:22:43 +0100
X-Sieve: CMU Sieve 2.2
Received: from localhost (localhost [127.0.0.1])
	by neo.wg.de (Postfix) with ESMTP id 90B632996C5
	for <[email protected]>; Fri,  2 Feb 2007 17:22:43 +0100 (CET)
Received: from neo.wg.de ([127.0.0.1])
	by localhost (neo.wg.de [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP
	id 12946-05 for <[email protected]>; Fri,  2 Feb 2007 17:22:30 +0100 (CET)
Received: from neo.wg.de (localhost [127.0.0.1])
	by neo.wg.de (Postfix) with ESMTP id B33592996C4
	for <[email protected]>; Fri,  2 Feb 2007 17:22:30 +0100 (CET)
X-Flags: 1001
Delivered-To: GMX delivery to [email protected]
Received: from pop.gmx.net [213.165.64.22]
	by neo.wg.de with POP3 (fetchmail-6.3.2 polling pop.gmx.net account
	551326)
	for <[email protected]> (single-drop); Fri, 02 Feb 2007 17:22:30 +0100 (CET)
Received: (qmail invoked by alias); 02 Feb 2007 16:19:13 -0000
Received: from mail.ammma.de (EHLO ammma.de) [213.83.39.131]
	by mx0.gmx.net (mx085) with SMTP; 02 Feb 2007 17:19:13 +0100
Received: from smtp.easydns.com (smtp.easydns.com [205.210.42.52])
	by ammma.de (8.11.6/8.11.6/AMMMa AG) with ESMTP id l12GI2110794
	for <[email protected]>; Fri, 2 Feb 2007 17:18:03 +0100
X-Greylist: Passed host: 216.63.144.209
Received: from ns1.ballandmourton.com (ns1.ballandmourton.com [216.63.144.209])
	by smtp.easydns.com (Postfix) with ESMTP id 71F504D228
	for <[email protected]>; Fri,  2 Feb 2007 11:18:50 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by ns1.ballandmourton.com (Postfix) with ESMTP id F10943863DD
	for <[email protected]>; Fri,  2 Feb 2007 09:54:05 -0600 (CST)
Received: from ns1.ballandmourton.com ([127.0.0.1])
	by localhost (mail.ballandmourton.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 14812-05 for <[email protected]>;
	Fri,  2 Feb 2007 09:53:51 -0600 (CST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by ns1.ballandmourton.com (Postfix) with ESMTP id E85543863DA
	for <[email protected]>; Fri,  2 Feb 2007 09:53:51 -0600 (CST)
Received: from adsl-70-142-46-77.dsl.tul2ok.sbcglobal.net
	(adsl-70-142-46-77.dsl.tul2ok.sbcglobal.net [70.142.46.77]) by
	mail.nwacg.net (Horde MIME library) with HTTP; Fri,  2 Feb 2007 09:53:51
	-0600
Message-ID: <[email protected]>
Date: Fri,  2 Feb 2007 09:53:51 -0600
From: Nathan Mills <[email protected]>
To: Jan Schneider <[email protected]>
Subject: Re: [whups] API calls
References: <[email protected]>
	<[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.1)
X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/)
X-Virus-Scanned: Maia Mailguard 1.0.1
X-GMX-Antivirus: -1 (not scanned, may not use virus scanner)
X-GMX-Antispam: -2 (not scanned, spam filter disabled)
X-GMX-UID: s1L2dPATbUko+qhaOmgnz7tkZ2hlN4r8
X-Virus-Scanned: amavisd-new at wg.de
X-Spam-Status: No, score=-2.599 required=5 tests=[BAYES_00=-2.599]
X-Spam-Score: -2.599
X-Spam-Level: 

Quoting Jan Schneider <[email protected]>:

> Zitat von Nathan Mills <[email protected]>:
>
>> Is there a particular reason that the show method only has a link    
>> parameter, rather than being fully implemented like the rest? It
>
> Yes, because that's the purpose of the "show" api methods.

Maybe I'm just being unobservant, but what's the recommended way to  
get info about one particular ticket? One can use  
get_assigned_ticket_ids to get an array of ticket IDs assigned to the  
particular user, but what then? The (seemingly) inaptly named  
getTicketDetails API call takes a queue and returns all the tickets in  
the queue.

-Nathan



--=_37shrcfs4h0k
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Whups mailing list - Join the hunt: http://horde.org/bounties/#whups
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]

--=_37shrcfs4h0k--