[JDEV] Redundancy and Backup Support

[Scott Robinson]

Interleaved response with sarcasm.

Scott.

* Paul L. McNeely translated into ASCII [Wed, Sep 15, 1999 at 01:03:45AM -0400][<000901beff37$b0c77b60$449ca8d0 at Marshall>]
> Just Curious, what if a persons home server goes down and they no longer
> have access to it for weeks on end, what do they do? [tear]

They get it connected again!

In a more serious tone, since this is a "home server" we must assume it isn't
the most reliable system. ;) I would like a clearer definition of "home
server" though. My "home server" will be an tunneling etherx with a "guise"
transport connected.

> [tear] Why not create the
> ability to mirror a server elsewhere and then the client can pick it up,

Mirror a server then a client can pick it up. What we're talking about it
fault tolerance. People spend _money_ on fault tolerance. What you want is a
"network" fault tolerance system where messages are queued up on other
servers in case yours is down.

I would like to take this point to point out we're talking about INSTANT
MESSAGING. We're a instant messaging and presense system. If you're not
online, it's a feature of jabbertransport to record your message. It is NOT
part of the protocol, nor is it to be expected. If your server is down, thus
you are down.

If I was to simplify your statement, it says "why not have a server where a
client can connect." 'Nuff said. If you want guaranteed queuing, the SMTP
network seems to be working.

> [tear] I'm
> still unsure how the back end of the servers work to transfer message
> between each other is it relayed like IRC or is just standalon that connedt
> to the specific server on a whim? [tear]

docs.jabber.org

> [tear] if it was relayed you caould set it up to
> allow them to log onto any server and have them send a special homeserver
> tag to grab the mirror.

Which I point to above in MY server setup. Of course, that special "home
server" seems to be remarkably similar to a normal client...

[snip]