yes and no. with many clients connecting to a single server you still have the problem of the connection to the server going away and your messages getting lost (or raising some sort of lost-connection error).
a way around this is a bit more work. each client machine also has a local jabber server, these local servers can then forward/communicate between each other. then as long as you can keep the local server running (to recieve messages from the local clients) you'll be ok. the servers can be configured (i think it's default) to queue messages for redelivery if the destination is down at the moment.
i'm planning to do about the same thing you want to do, i've been waiting for jabberd2 to settle down a bit, for the core protocols to make it through the IETF, and for working Kerberos/SASL Authentication before i make the jump.
In reply to Re: using jabber for RPC or inter-server-communication
by zengargoyle
in thread using jabber for RPC or inter-server-communication
by schweini
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |