From: Ken Lalonde <ken@to...> - 2002-09-13 17:04:52
WebKit isn't as efficient as it could be when
serving static content. Although it caches non-huge
files, it doesn't make use of a much more powerful
caching method: the If-Modified-Since HTTP header.
Of course, moving your static content to a separate
HTTP server is fastest, but supporting If-Modified-Since
buys most of the benefits for little cost.
I've uploaded a patch to sourceforge.net/projects/webware/
(patch id 608957). The patch modifies mod_webkit.c to make the
If-Modified-Since header available to the AppServer,
and changes UnknownFileTypeServlet.py to make use of it
(i.e. no content is sent if the file hasn't changed).
It works quite well.
Given IMS support, I see little point in caching content
in the AppServer. I suggest changing the CacheContent
default setting in Application.config to 0.
- Ken Lalonde
Get latest updates about Open Source Projects, Conferences and News.