[JDEV] Theoretic.com Now Blocked
Max.Metral at PeoplepcHQ.com
Tue Jan 8 15:05:17 CST 2002
Both of these schemes require client knowledge of the vagaries of the AOL
protocol. What about a more utilitarian approach where essentially the
client is JUST a pass through to the server? It passes ALL traffic (either
over the single jabber socket or over a separate one (probably not worth it)
) back to the server, the server interprets, and returns any actionable
stuff to the client? I know the perf isn't great, but it keeps the nice
goal of keeping the clients out of protocol mess.
From: Mathew Johnston [mailto:mjohnston at itactics.com]
Sent: Tuesday, January 08, 2002 3:51 PM
To: jdev at jabber.org
Subject: Re: [JDEV] Theoretic.com Now Blocked
We could also make a little stripped down AIM transport in Perl, Ruby or
something that will sit on the machine of every client and accept
connections only from localhost. Thus AIM sees one connection per
client, and does not suspect Jabber.
On Tue, 2002-01-08 at 12:51, Michael Rothwell wrote:
> Perhaps the jabber server could hand out a referral to the client for a
> transport -- "Use this other server for that" -- and jabber.org could keep
> list of alternate AIM/ICQ providers.
> Or, the aim transport on Jabber could still keep the list of other AIM/ICQ
> servers, but handle the connections through them itself.
> That way, the AIM/ICQ load would be distributed.
> Perhaps the jabber server could have an option to send, and listen for,
> alternate transport providers. Then when we all setup AIM and ICQ
> transports, they can announce themselves to the jabber.org server.
> Jabber.org can perhaps keep some statistics on the reliability and number
> connections of each remote transport, to keep service available and under
> ----- Original Message -----
> From: "Kevin Smathers" <ks at micky.hpl.hp.com>
> To: <jdev at jabber.org>
> Sent: Tuesday, January 08, 2002 12:38 PM
> Subject: Re: [JDEV] Theoretic.com Now Blocked
> > 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
> > 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
> > > 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
> > > > transports. This is quite a bit more complex than installing and
> > > > running a client.
> > > >
> > > > Cheers,
> > > > -kls
> > > >
> > --
> > // .--=,
> > .....::://::::::::::::::::::::::::::::.. (o O & kevin_smathers at hp.com
> > :::::::://:::://://://:/:://::||_// / V K
> > :::::://:::://:/:|//'/' // _,|' r , 'qk
> > :'''/____ // / // |_// // || .'~. .~`,
> > kls \_/-=\_/
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> jdev mailing list
> jdev at jabber.org
jdev mailing list
jdev at jabber.org
More information about the JDev