Re: Inline content modification?

Robert Collins wrote:

> BTW: client_side is good for filtering too - I was pointing out that for a accelerator that alters every request with those URL's,
> server sided is more efficient. For altering based on username/client-agent or a number of other things, client_side is more
> efficient. What I'm building hooks filters in at four different locations: incoming data request & response, outgoing data request
> & response.

A small warning about server-side content modifications: If you intend
to peer with others, then server-side content modifications is generally
a bad idea. This because the cached modifications are on the real URL,
and your peers won't be able to distinguish between rewritten and
original content for those URIs.

For an accelerator it makes sense to do it on the server connection.
Especially so if the accelerator is set up without URL rewriting (see my
recommendations on accelerator setups)

For a transforming proxy without URL rewriting it makes sense.

For a transforming proxy with URL rewriting it is a bad idea, and is
better done in the client side.

For an accelerator farm where the farm members peers with each other
care needs to be taken so the content isn't modified multiple times by
each accelerator in the object path.

/Henrik
Received on Wed Jan 17 2001 - 02:03:49 MST