Serving resources dynamically is in fact beneficial when it comes to
controlling cache behaviour. I usually insert a version number into
the URL to files, so when a file is modified,it's URLs changes too.
This allows you to set cache headers so that resources are cached
virtually forever and only fetched when a change has occurred and a
new version is required.
An additional benefit of this is that a user's browser will never be
using an out of date version of the resource. Quite nice.
OTOH, I DO live in Iceland and develop sites for a market of 300.000
people - so I am allowed to do some wacky stuff when it comes to
performance ;-).
Cheers,
- Hugi
On 30.11.2008, at 18:46, Guido Neitzer wrote:
On 30.11.2008, at 11:03, Chuck Hill wrote:
You will also have to make sure the headers are set to allow client
caching (which is usually not what you want for dynamic content) or
the users will have to wait for for CSS to be downloaded again on
every page. That is also a performance issue, but on the other
side of things.
And on a busy site that's a big one. Same for "design" images
(buttons, corners, backgrounds, icons) and so on. That can easily go
over 10GB per day if you have a public and busy site.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
