[Flickr APIs] RE: Flickr-APIs digest, Vol 1 #6 - 4 msgs

Thanks for your input, Cal. We've not ventured as far as the rest of the
APIs yet, so we may need to revisit this later, but our current thinking for
the Upload method is to return the ID of the photo on success or throw an
exception on failure.

I suspect that for the main API methods we will return a structure
containing the fields of the response, but still throw an exception on
failure.

We've now set up a GotDotNet Workspace
(http://workspaces.gotdotnet.com/flickrdotnet) to host our project. Rather
than type all the information out again I'll point you in the direction of
my blog, where I announced the start of the project:
http://blog.salamandersoftware.co.uk/archive/2004/08/24/186.aspx

Derek.

-----Original Message-----
From: "Cal Henderson" <cal-YBANsMgXN/7QT0dZR+AlfA@xxxxxxxxxxxxxxxx>
To: <flickr-apis-PH6dntW41FXEJFt6QFEIHw@xxxxxxxxxxxxxxxx>
Subject: Re: [Flickr APIs] Flickr .NET Library
Date: Mon, 23 Aug 2004 10:39:08 -0700
Reply-To: flickr-apis-PH6dntW41FXEJFt6QFEIHw@xxxxxxxxxxxxxxxx

: I'm posting here (and in the API Group
(http://www.flickr.com/groups/api/))
: to prompt a discussion on how (and what) we should return from our
methods.

the perl api kit returns a structure containing a few things:
http://search.cpan.org/~iamcal/Flickr-API-0.02/API/Response.pm

the request that was made and the success status of the request are the main
elements. if the request was sucessful then the 'tree' slot is filled with a
parse tree of the xml response. if the request failed then the error code
and message slots are filled.

this allows us to change the transport behind the scenes (rest, xmlrpc,
soap, whatever we add) and the interface will stay the same. returning a
single value is of little use for the data fetching methods. perhaps in the
C idiom you'd return a success bool and have an in/out parameter that gets
filled with a response object as detailed above.


--cal