<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45"> <TITLE>RE: [JDEV] Disney Jabber Client</TITLE> </HEAD> <BODY> I'm sorry I missed most of this thread. > Ben Schumacher write > > somone else wrote > > Last I heard, they were having trouble with the s2s setup.  > > Primarily the fact that servers doing dialback would try > > and contact go.com but their IM is running on im.go.com.  > > The in-ability to reroute the traffic within the Jabber > > standards without resorting to DNS workarounds had been a > > bit of a bummer.   > I believe this is not correct, anymore. They are using some sort of > redirector on their network to route the packets. When they > first brought up the server, it was on im.go.com, but now that its > basically live, they have moved everything over to use just go.com and > use a layer 4 switch to route the traffic to the correct host. (At > least, that is my assumption.) We would really love to have the server-to-server stuff running.  I thought that we were waiting for the abber.com commercial s2s  software to be completed before we could set it up.  I know in the past there was some issues with Our network setup, but I had thought those were resolved.  I'll ask my boss what is going on.   > > I think they had the ability to do the technical hack but preferred to > > try and create an elegant solution rather than rush it.  In addition, > > their primary goal is to provide IM between disney users so s2s isn't > > the number one priority...  My impression is their IM team is very > > small so most of the effort is going into the disney client. > > I think you're probably right on the issue of the IM team being small, and > I know they have tried to get S2S (SCM) working, however, like many other > corporate networks, they are worried about potential abuses on their > network from external servers. (At least, that is my impression.) Team?  Its really just me with some parttime design support and the Occasional  Help from network operations.   > Hopefully they'll get S2S (SCM) up and running soon as I think it would add > a lot to the Jabber community. I really hope so too! BTW, its been a while since I've done a release.  I'm almost ready to make a new release that will include support for message history SSL the new text-conferencing, etc. -Robert </BODY> </HTML>