Monday, March 01, 2010

How to server static content

From a performance perspective, the trouble with cookies is that once the server sets a cookie for a particular domain, all subsequent HTTP requests for that domain must include the cookie. Even if the server has no use for the cookie, as is usually the case with static components, the cookie is sent over the wire anyway, bloating our request headers with useless code.

So serving static content (e.g. images, css etc.) from a cookieless domain is a standard performance best practice. See more details here.

And JSOS provides several components lets you share your content across several servers. See for example: Load balance and Moved permanently servlets.

No comments: