Originally Posted by bonerton
So then I'd separate everything into different html files? Like sidebar.html, content1.html, content2.html... etc, and then compile then in my index.html? Sorry, i'm a total n00b. I feel like i've googled the **** out of this and gotten so many ajax books at the library that go into detail, but i'm still missing some simple step. thanks for your reply.
there are three typical approaches to this task:
1. server-side processing. This is where you use simple SSI, PHP, ASP, etc to bundle pages together into a single file right before it's delivered to the client.
pros: always updated, single file delivered to client, good client performance.
cons: server processing lowers the # of clients per hour you can serve.
2. client-side processing. This is where AJAX or JSONP is used to inject content into an HTML shell. My blog is an example.
pros: always updated, less work for server than includes, allows part caching.
cons: slower client performance, more prone to caching problems.
3. templating. this is the procedure used by editors like dreamweaver templates and library items. The separate files are combined by the editor and saved into a single HTML file which is then served to the client.
pros: lowest server resources of all methods;highest # of clients per hour. single file results in high client performance.
cons: not self-updating, editor must run a site update to update the built page with new/altered content.