AFAICT, this has nothing to do with the technical merits of the application, but rather with the correctness of the term. The name is the easiest thing to fix. ESME might not be using the name "REST" correctly in the strictest sense, but neither are most of the popular "terms", such as Ajax.
I don't want to sound dismissive, but I've seen more scathing remarks about the correctness of REST: http://java.dzone.com/articles/rest-http BTW, where can I see the response in the yahoo group? On Sun, Dec 21, 2008 at 5:48 PM, Hirsch, Richard <[email protected]> wrote: > Please read the whole thread from the yahoo group message. I've commented and > ask them to join the conversation at esme-dev. > > D. > > ________________________________ > > From: Hirsch, Richard > Sent: Sun 12/21/2008 13:23 > To: [email protected] > Subject: Pretty scathing critique of our REST API > > > > Just found this after following a link on the scala reddit > (http://www.innoq.com/blog/st/2008/12/esme_twitter_clone_in_scala.html) > > http://tech.groups.yahoo.com/group/rest-discuss/message/11862 > > "Esme's API is as bad anything I saw in the SOAP/XMLRPC days. I'm dumbfounded > this can get incubated in the ASF." > > Yikes. > > D. > > > >
