4 ms·
The static thing - I think its a reaction to the obvious inefficiency of dynamic pages, server processing for data that is only changed occasionally. Consider
by dpweb 13y ago
The static thing - I think its a reaction to the obvious inefficiency of dynamic pages, server processing for data that is only changed occasionally.
Consider a blog which gets posted to once a week. Do you really need dynamic processing for every page render 24/7/365? Well, that's the way it works.
But you have to have something additional for changing data/separate API. You can do the static site, but you still gotta have the XHR or JSONP calls to fetch dynamic data. You get a nice separation of UI/data, easier to tweak the UI - independent of the data (hand it off to a designer), and your separate data server can feed multiple apps or you open it up for the world to use.
- snowwrestler 13y ago> Consider a blog which gets posted to once a week. Do you really need dynamic processing for every page render 24/7/365? Well, that's the way it works. Isn't this the exact problem that a reverse proxy cache solves?
- dpweb 13y agoit does if you want to setup the 2nd piece, but I like nginx alot