On Thu, 05 Oct 2006 08:52:45 -0700, Dave Crocker <dhc(_at_)dcrocker(_dot_)net>
wrote:
Steve Atkins wrote:
Given that jabber appears to be not ready for
prime time, in oh so many ways, has anyone
considered using a more reliable technology?
Sorry, Steve, but I do not know of any problems with Jabber/xmpp
technology, and its overall track record for IETF use has been
excellent. Further the range of free client software seems quite good.
The problem we are having is operational, with a donated service. (And,
by the way, it's rarely been a problem during IETF week, so this is not
a case of reaching some sort of limit.)
If you know of other problems, what are they?
I don't know what happened here, but I've seen other Jabber problems at
close hand. The problems tend to involve synchronization between the two
servers.
If you have an account at jabber.org and try to talk to someone (or a
chat room) at jabber.ietf.org, the data flows from you to jabber.org, and
thence over a multiplexed channel to jabber.ietf.org. From there, it
would go to your correspondent, or to the chat room server. But
sometimes, due to buggy software, the two servers get out of sync, or one
will think the connection is up while the other thinks it's down.
There's not much that can be done then, with the servers I've played
with, except to restart one or both of them.
On a more systemic note, I've seen some servers that don't do well with
SRV records. Yes, I know they should....
--Steven M. Bellovin, http://www.cs.columbia.edu/~smb
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html