Server Caching: Difference between revisions

Revision as of 07:07, 29 May 2007

This page discusses a number of issues surrounding caching of (HTTP) data locally on school servers.

Software to use for caching. The current possibilities are

Lighttpd [1] -- Why?
Polipo [2] -- Recommended as an alternative by the Tor developers since it works well for them in an environment that is in many ways similar to ours. Polipo is fast and small (one binary file)

Caching materials after viewing

One laptop caches locally, both in memory and on disk (in case of failure?)
A set of laptops sharing a cache that's too large for any individually
A server caching and aggregating caches from individual machines -- can it uptake cached materials if a connecting laptop has something in its cache that's not on the server?

Queuing requests

A laptop requests something from a local cache;
A cluster of laptops listens to requests from individual laptops in the cluster;
A server listens to requests from connected laptops (directly, or passed on from others not currently on the mesh)

Caching requests without viewing

A laptop passes on a request, a server picks it up while the laptop is off-mesh and caches the result
Some sort of notification or syndication of the incoming material

@@ Line 4: / Line 4: @@
 Software to use for caching. The current possibilities are
-* Lighttpd [http://www.lighttpd.net/]
+* Lighttpd [http://www.lighttpd.net/] -- [http://www.linux.com.cn/modcache/ Why?]
-* Polipo [http://www.pps.jussieu.fr/~jch/software/polipo/]
+* Polipo [http://www.pps.jussieu.fr/~jch/software/polipo/] -- Recommended as an alternative by the Tor developers since it works well for them in an environment that is in many ways similar to ours. Polipo is fast and small (one binary file)
 == Questions about School server caching ==