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. even with a client-side framework like bootstrap, I still prefer to generate the html from jade templates, it allows for better Modularity. "just" serving up data really isn't all that trivial... On Feb 17, 2012 7:16 PM, "Moandji Ezana" <[email protected]> wrote: > 2012/2/17 Cédric Beust ♔ <[email protected]> > >> This is another important aspect for a web framework, in my opinion: >> being template technology neutral. > > > Since any decent templating engine can easily be invoked programmatically, > I don't even see a reason for a server-side framework to make any > templating choice at all. > > For modern web applications, I don't really get the point of server-side > frameworks that do more than serve up data. > > Moandji > > -- > 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. > -- 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.
