[JDEV] AT&T beating us to the punch..

[Thomas Charron]

Quoting Isotope2k at aol.com:
> In a message dated 12/9/99 11:47:11 AM US Eastern Standard Time, 
> ebowersox at corp.webb.net writes:
> > Makes me wonder if a Jabber AIM transport is really a good idea, or if
> it's
> >  just an exercise in futility, as AOL seems determined to throw monkey
> >  wrenches into the works of anyone trying to interoperate with them...
> I'd say it really depends on how they are blocking the connections.
> If they are doing it based on the IP address of the servers- well, tech
> savvy AOLers can host servers too. :)  Furthermore, as more and more
> people add Jabber to their various offerings (it will happen, Jabber is
> a strong technology), you will see the widespread adoption of an
> open standard, making AIM the odd man out.  

  AIM uses an overflow bug to detect clients that aren't made by them..

  Hrm.  Has anyone actually tried to look at what the overflow bug causes, 
and 'emulate' it?

> When Jabber is done, I don't imagine that the IETF standard will be
> too far behind.  Most of the major IM vendors are purported
> to claim that they will support that standard, as will Jabber.  That makes
> much of these actions a moot point.

  We'll be up to 1.0 long before any IMPP standard is released.

  Sooner then you'd think.. ;-P

--- 
Thomas Charron
<< Wanted: One decent sig >>
<< Preferably litle used  >>
<< and stored in garage.  ?>>