On Mon, 2 Jun 2003, James Gregory wrote:
> > >> 3. There must be NO DISCERNABLE INTERRUPTION TO SERVICE when one
> > >> fails. Doing a "shift-reload" in the browser is NOT an option. It
> > >> must be TOTALLY TRANSPARENT.
> >
> > James> Wow. Well, point 3 makes it pretty hard. As I understand it,
> > James> that's an intentional design decision of tcp/ip -- if it were
> > James> easy to have another computer interrupt an existing tcp
> > James> connection and just take it over, then I'm sure it would be
> >
> > If you're only serving static content, that's not an issue: HTTP
> > version 1 uses a new tcp/ip connexion for each request anyway,
> > With round-robin DNS you may end up with different images on the same
> > page being served from different servers anyway.
>
> Sure, that's a given. I thought the problem was that it had to happen
> without a reload - server crashing halfway through serving a particular
> html page. I considered 0 ttl dns as well, but it only works if you can
> afford reloads.
I suppose you might be able to hack something together with MIMEs
multipart/x-mixed-replace in a proxy which monitored content length and
was ready to fetch a second MIME part where required. It would be a bit
messy though, not necessarily compatible with all browsers, and the proxy
is still going to be a single point of failure.
Andrew McNaughton
--
No added Sugar. Not tested on animals. If irritation occurs,
discontinue use.
-------------------------------------------------------------------
Andrew McNaughton In Sydney
Working on a Product Recommender System
[EMAIL PROTECTED]
Mobile: +61 422 753 792 http://staff.scoop.co.nz/andrew/cv.doc
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
