[JDEV] Disney Jabber Client

Iain Shigeoka iainshigeoka at yahoo.com
Mon Jan 14 11:53:32 CST 2002

On 1/12/02 1:33 PM, "Ben Schumacher" <ben at nanotopia.com> wrote:

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

That's good.  I was only keeping up with them when they were in beta and
rolling out the system for testing.  I was curious to see how the rollout
went and the kinds of issues they were running into.  Now that its in
production use its not as interesting... (A well oiled machine is kind of
boring...)  :)

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

Yes.  I have been wondering about those issues (many of which are
political/business/legal and not technical).  For example, are there
"rights" to Jabber s2s access, service level agreements, usage policies,

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

I agree.  In addition, it would be interesting to see how well it works in
practice with such a large new addition to the Jabber network.  Hopefully it
won't be like the Gnutella meltdown...  ;)


Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

More information about the JDev mailing list