I have a strong requirement for a REST-ful scheme, with some flexibility on the definition of REST-ful. One thing I didn't
Remember that we can't break existing URL schemes. So essentially we are talking about replacing the current URLConstructor scheme with another URLConstructor scheme, which may or may not rely on Stripes artifacts.
IMO RESTful has become an overloaded hypeword these days. You can look at it this way: we already *are* RESTful. *All* applications which use the browser are RESTful. REST does not mean "we will not use query string". REST means that every resource is accessible through an unique link (and that it's stateless, which we mostly are anyway).
When it comes to the machine-accessible APIs, then REST becomes a far more useful paradigm (as opposed to things like XML-RPC and SOAP). There is no single endpoint, but you use the same kind of an API to access your data as with the regular browser.
/Janne
