photos.getFavorites ?
|
June 05, 2008, 03:41 PM
|
|
I was following the thread http://www.23hq.com/forums/message-view?message_id=3165665 and thought about coding that group-favorites-thingy, but to my surprise photos.getFavorites isn't available in the API? Just wanted to note this for a rainy day ... :)
|
| |
|
Team 23
June 05, 2008, 04:23 PM
|
|
That probably makes it hard to implement that feature ;-)
I'll take a look at it. The main concern at the moment for api in the php_serialized format. We'd really like to support it, but flickr has something of a head start since the service is php native. The format is pretty hard to emulate, and we'll probably need to re-do the api implementation from scrath to have php and json supported.
Look for a fourth format option, tcl_list, when we get there.
|
| |
|
June 05, 2008, 04:33 PM
|
|
Ah, which language is 23 written in? And isn't there a library that implements PHP's serialize in that language? (e.g. I found one for Ruby with a Google search)
|
| |
|
|
Team 23
June 05, 2008, 05:24 PM
|
|
|
|
| |
|
|
June 07, 2008, 12:56 PM
|
|
OK, there's one I didn't see coming... Best of luck then :P
|
| |
|
|
Team 23
June 07, 2008, 01:03 PM
|
|
In fact the biggest problem isn't converting between formats -- instead the issue is the there isn't a 1:1 correlation between, say, XML and JSON.
In XML, you'd have:
<photos>
<photo photo_id="678"/>
<photo photo_id="2341"/>
</photos>
The obvious conversion is:
photos:{photo:{photo_id:678}, photo:{photo_id:2341}}
(which wouldn't work)
Instead, it has to be translated into:
photos:{photo:[{photo_id:678}, {photo_id:2341}]}
I'm actually feeling pretty confident that we'll be able to release the JSON-version of the API quite soon. The TCL LIST format is ready as well. The PHP thing, though, still ticks me off ;-)
|
| |
|
|
Team 23
June 07, 2008, 01:39 PM
|
|
On a related note: Does anyone know of flickr projects with which is can test the format=json code?
|
| |
|
|
Team 23
June 07, 2008, 06:58 PM
|
|
|
|
| |
|
