[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Dynamic content and tux



Hi,

Most access patterns on a site hosting dynamic content has the following
form:

- request dynamic page (let's say index.php)
(browser parses page, discovers images)
- request static img
- request static img

Now, the first request forces tux to pass the request and the socket to
apache (or similar), and if persistent connections are used, the following
two (static) requsts will also be handled by apache. It seems tux is of
little use here ...

You could configure apache not to use persistent connections, forcing the
browser to reconnect for the images, but then the question is: is the
overhead of accepting a new connection worth using tux?

Any ideas on the subject?

Greetings,

Nick Hofstede






[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []