On Wed, Jul 9, 2008 at 4:06 PM, Nick Stuart <[EMAIL PROTECTED]> wrote: > Ok Remi, we get it, you don't like REST wont use REST and think it sucks, > but unless you have some constructive feedback here you are not contributing > to the cause. [...]
You're kidding ? I've posted a full email about this ! And you'll note that nobody yet answered the magic question : what's the purpose ? I'm trying to avoid people jumping into the REST trap too fast, as there are precisely simpler ways to achieve the same goal, which is : > For REST/Stripes integration I definitely see it as more as way to allow > Stripes apps to talk with other apps/services in a standard way. You can have your Stripes app *fully* invokable from any standard HTTP client that understands JSON or XML, without *any* modification of your existing logic. We already have such thing working since a while now. Even better, for those who know a bit about middleware, the approach allows to dynamically generate documentation and interface descriptions, thus making Dynamic Invocation possible (which I believe would work as well with Will's approach, as it uses reflect to introspect the bean's events etc.). Really, no need for verbs or other bullshit, sorry. This is "fly fucking" again :-P And again, don't be offended by my language, that's just how I am. Think about the content, not the appearance : isn't proposing alternatives "contributing to the cause" as well ? 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
