[JDEV] Theoretic.com Now Blocked

[Julian Fitzell]

But having each client make its own AIM connection sort of goes against 
the whole Jabber architecture.  The whole point is that the client is 
simple, makes one connection, and the server routes everything.  If you 
want a client that does Jabber and AIM and ICQ by making a seperate 
connection for each, there are other clients out there that do that - 
but they implement the AIM and ICQ stuff in parallel to the Jabber 
connection, not on top of it.

Julian

Kevin Smathers wrote:

> True, but that doesn't solve the problem of AOL firewalling ports of
> servers that become popular.  My point was that only by having each
> client act as their own AIM transport will you make it effectively 
> impossible to firewall Jabber since each client will be indistinguishable
> from a normal AIM client.  
> 
> If lots of traffic is being concentrated through a single IP, it is
> pretty easy for AOL to figure out that something odd is going on.
> Spreading that load out to the edges would effectively remove the
> marker.
> 
> Cheers,
> -kls
> 
> Btw: I understood what you meant by home server, I just thought that
> you knew what I meant when proposing to move the transport out to the 
> client.
> 
> On Tue, Jan 08, 2002 at 11:16:59AM -0600, Peter Saint-Andre wrote:
> 
>>I think you misunderstood. By "home" server I meant the server you
>>normally connect to (in my case, jabber.org). Just because I use the
>>jabber.org server doesn't mean I can't register with the transports on
>>another Jabber server. And in fact that is what I do for connectivity to
>>AIM and ICQ.
>>
>>Peter
>>
>>On Tue, 8 Jan 2002, Kevin Smathers wrote:
>>
>>
>>>Hi Peter,
>>>
>>>These aren't quite the same thing.  Running a personal server means 
>>>managing the server, managing logins, managing security, and managing 
>>>transports.  This is quite a bit more complex than installing and 
>>>running a client.
>>>
>>>Cheers,
>>>-kls
>>>
>>>