On Thu, Jul 10, 2008 at 3:07 PM, Nick Stuart <[EMAIL PROTECTED]> wrote: > See Remi this is where I get confused. You say REST makes everything more > complicated and that POST is enough.
Yep, and this whole thread kinda proves me right : RPC over HTTP is already easy, simple and effective (for simple use cases of course) with stock Stripes (and some other fwks) and you-name-it Java->XML/JSON/whatever serialization toolkit. Using Stripes events, it even resembles a method call : POST or GET http://.../myapp/myservice?p1=v1&p2=v2&myevent -> JSON Simple, easy, working. Even a first year IT student gets it in a few seconds. You don't even need to know about HTTP methods. Now, on the other hand, there are guys having endless talks about specs, verbs, nouns, RESTful URLs and other philosophical considerations. Man, by the time they all agree, I already have 5 webapps shipped and running :) And they have no dep on you-name-it fwk, almost no code or config for the RPC plumbing, and thus are easier to maintain... Again, the question is dead simple : what use case does REST cover best than then aforementionned "do it yourself" technique (knowing that Stripes does 99% of the do-it-yourself thing, the most crucial part being binding and validation) ? Until somebody has a good answer, sorry, I'll still think this REST story is nothing but FUD. > As Will pointed out REST can be thought of as a > 'lightweight' SOAP for a lot of things. Again, already seen the movie. SOAP and the WS-* stack was the title if I remember well. They started by claiming they had a "lightweight" CORBA, and at the end of the movie they ended up with a pale, deficient clone of it. Needless to say, this movie sucked big time. Now REST lighter than SOAP ? Well, my proposal is even slicker :) > If you want to make it really dumbed > down just think as REST as kind of a automatic Action mapper for incoming > requests. ... an Object Request Broker :) Jokes aside, isn't that exactly what Stripes already does (or more exactly part of what it does) ? > Also, I do want to say that I know REST doesn't fit everywhere and wouldn't > make sense to use everywhere. Heck, most of our app here doesn't and wont > use it, but there are some parts where it would fit nicely. I am not saying > REST is a magic bullet, and I do agree that people that think that way are > going a little to far, but I can a place in the great expanse of intertubes > for it. Here lies the answer to my question : where ??? I mean, where would it fit nicely ? That's precisely why I'm not sold on REST : I fail to see even the beginning of some place where it would fit :-P Cheers Remi ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
