> For example, for me Flickr's API is great but I love the security of Del.icio.us.
Flickr's API is the best I've seen because... * Beautifully structured documentation * Fast * Loads of methods * Methods added regularly * Well supported by the community with kits and examples in *many* languages * Highly persuasive data (photos of me and my friends) I guess half of this is caused by the fact that the AJAX goodies on flickr.com itself acquire data from the API. I didn't like del.cio.us' security. Whilst I appreciate the use of the standard HTTP Authentication it presented a barrier between me and the data. I'd rather pass my authentication info as another argument (a la Flickr) rather than messing with HTTP authentication [1]. Del.cio.us often runs slowly, which can't be helped by all API requests go over HTTPS. I'd argue HTTPS isn't really needed anyhow - its not like its my credit card details we're talking about, just my already public bookmarks! J [1] When I consumed the del.cio.us API I was using ASP.net, which required the use of System.Net.NetworkCredential and System.Net.WebRequest to pass the HTTP Authentication details. Not a big deal it turns out - but more hassle and different to all the other APIs I had consumed in the same app. Just annoying. ________________________________________________ Jason Cartwright Client Side Developer - CBBC Interactive [EMAIL PROTECTED] Desk: (0208 22) 59487 Mobile: 07976500729 "Recreate the world in your own image and make it better for your having been here" - Ray Bradbury - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
