* Toni Mueller <openbsd-po...@oeko.net> [090118 11:42]: > > Hi Jim, > > thanks for posting. > > On Sat, 17.01.2009 at 23:06:38 -0500, Jim Razmus <j...@bonetruck.org> wrote: > > I dropped the maintainer line from the Makefile. I've gone with Movable > > Type and don't need or want an HTTP accelerator anymore. > > This caught my curiosity. What were you using Varnish for, before? > > I'm also in the situation to host Movable Type, but as of late, got > rather disenchanted with it. > > > -- > Kind regards, > --Toni++ >
Varnish is a reverse caching HTTP proxy more or less. It allocates a chunk memory and then caches the output from backend web servers to serve future requests itself. It's like squid, but arguably more efficient and scalable. Varnish could be advantageous when used in conjunction with truly dynamic web applications. Word Press and Plone I believe create everything dynamically for all requests. They have caching plug-ins available though... Movable Type creates static html files for subsequent delivery by your web server. The "dynamic" nature of Movable Type only comes about when creating a new entry/page and/or adding a comment to a page/entry at which time it just creates an updated html file. Any decent web server should be able to choke your Internet connection serving static content from the file system. So Varnish is mostly redundant redundant in this case. Varnish has some other capabilities for integrating with ESI services, normalizing http request headers, front ending a web/app server farm, clever cache refreshing, etc. None of which do I need or can use. HTH, Jim
