If the "dynamic" content is just e.g using different layouts/themes according to the client, then you can put all that logic in Javascript - possibly using redirects to a small number of alternatives.
Then keep the server-side HTML and images static. For more advanced work, you want to look at tools like angular.js - make the json/RESTful endpoints more dynamic but not the HTML. On 5 February 2014 14:44, Rakesh <[email protected]> wrote: > I don't understand this? If i need to serve dynamic content then....I > need to serve dynamic content! > > Rakesh > > On 5 February 2014 14:30, Fabrizio Giudici > <[email protected]> wrote: > > On Wed, 05 Feb 2014 15:21:03 +0100, Kevin Wright < > [email protected]> > > wrote: > > > >> If you're thinking to serve dynamic content, then don't! It really > messes > >> with caching, CDNs, etc. A much nicer approach is to have distinct > >> resources and run the logic on the client to determine what to fetch. > > > > > > +1 > > > > > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/javaposse. For more options, visit https://groups.google.com/groups/opt_out.
