[JDEV] Disney Jabber Client

[Ben Schumacher]

At 11:28 AM 1/12/2002 -0800, you 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.)

>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.)

Hopefully they'll get S2S (SCM) up and running soon as I think it would add 
a lot to the Jabber community.

Ben