3 ms·
The OP is completely correct. I designed a bunch of the Windows Azure APIs - we spent a lot of time making sure they were RESTful. Looking back now, I think it
by sriramk 16y ago
The OP is completely correct. I designed a bunch of the Windows Azure APIs - we spent a lot of time making sure they were RESTful. Looking back now, I think it was a big waste of time. Almost everyone uses the API through some custom library and I doubt it would have mattered if we hadn't taken the trouble.
I'm involved in some API design again and I sent out a mail saying that any discussions involving whether option A or option B is the more 'rest-ful' thing to do will get smacked down :)
- aaronbrethorst 16y agoHey Sriram - When are we getting coffee? I'll code against Amazon's gnarly API because I have to, not because I want to. Flickr's another great example of this. I mean, seriously, look at some of the calls, here: http://www.flickr.com/services/api/ http://www.flickr.com/services/api/ I think it's way more logical to POST a photo_id to http://flickr.com/galleries/123456/photos http://flickr.com/galleries/123456/photos than to POST to http://www.flickr.com/services/rest/?method=flickr.galleries.addPhoto&api_key=123456&gallery_id=123456&photo_id=98765 http://www.flickr.com/services/rest/?method=flickr.galleries... (note: HN is truncating the displayed link.) Then again, I don't think I'm in the target demographic for Azure.
- rimantas 16y agoSo you don't care about those writing custom libraries?