On Fri, 17 Feb 2012 20:29:30 +0100, Kevin Wright
<[email protected]> wrote:
This is certainly the REST ideal, but it's not so simple as it sounds.
Even
in a rich-client environment you can still expect back end servers to:
Handle json serialisation/parsing
Manage routing to restful endpoints
Perform caching and gzip compression
Co-ordinate chunked http streams
Convert coffeescript to Javascript
Convert less/sass to CSS
Minify/aggregate resources
Marshall data across domain boundaries
Authorisation/authentication/oauth/ssh termination
Etc.
Agreed. My ideal requirement is that the web framework, starting from
Cédric's principles, has got a core that only serves data, as Moandji
said. All the other things should be provided by add ons (libraries,
plug-ins, etc...) that I only add when I need.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
[email protected]
http://tidalwave.it - http://fabriziogiudici.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
