| From: | "Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx> |
| Date: | Mon, 30 Oct 2006 19:01:38 +0100 |
[redirecting to users@] Matthew Dillon wrote: > The solution was to have a couple of cookie-cutter boxes front-ending > all the WWW connections, doing the first few protocol interactions > (e.g. processing the WWW command and the Host: header), then > looking the info up in a DBM and reconnecting to the actual machine. [...] > > * It didn't matter which machine handled a connection. Each machine > was an exact cookie cutter copy. A DBM update was pushed out to > the boxes once an hour via cron. > > * I could add or remove machines at will. Bandwidth and loading was > never an issue. We never needed more then 3 boxes, though. How did you dispatch between those boxes? Use a round-robin DNS, or something more sophisticated? How did you relay the data on those boxes? Just simple poll/read/write cycles? I realize that you just said that it just added 2ms delay, but doesn't the transferred data get copied several times around in the box? What's the fuzz about zero-copy then, if this copying doesn't matter? cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Attachment:
signature.asc
Description: OpenPGP digital signature