[jdev] Google Talk transport?

[Norman Rasmussen]

I'm not that up to speed with the Perl Jabber libraries, so please
excuse me if I'm wrong here.  When I got around to implementing a
transport is going to be in python, because I'm familiar with that.

I was going to make one client connection per-resource.  So basically
if you login twice, you proxy twice too.  Wouldn't that get rid of the
"Handling of the Resource portion of the JID is at times crufty"
comment?

Also why not move to data forms to address "Certain clients silently
drop some of the tags requested for registration.".  That way you can
make your own fields, and things will just-work(tm).

On 04/10/05, Bruce Campbell <list-jdev at vicious.dropbear.id.au> wrote:
> On Mon, 3 Oct 2005, Norman Rasmussen wrote:
>
> > On 03/10/05, John Talbot <jtalbot at proionta.gr> wrote:
> >> Norman Rasmussen wrote:
> >>> I was thinking of making a general XMPP transport for jabber.  You
> >>> would have to register with it to supply your gtalk account details.
> >>> Also when you set it up on your server you would override the
> >>> @gmail.com with the transport, and then all your google talk stuff is
> >>> 100% transparent to the user after he has registered.
> >> ...but why the phrase "was thinking"? Aren't you thinking of going ahead
> >> anymore?
> > I'm hoping that google will enable s2s before I have time to code it :-P
>
> Doesn't look that hard.  JEP 100 documents most of the cases.
>
> Actually, it wasn't that hard.  You can download a simple version at
> http://zerlargal.org/c/xmppgateway.pl .
>
> As-is, it probably will _not_ work for realtime conversations with Google
> talk, but enterprising people will understand what line 191 does and be
> able to work around it.
>
> Known Bugs:
>
>         PSI drops certain fields in the registration, Gabber doesn't.
>         This makes registering with the gateway a touch difficult.
>
>         Its a 1 to 1 mapping; a given client cannot register multiple
>         times to different remote networks.
>
>         The polling is crufty, and I wouldn't be surprised if it managed
>         to mix up messages when gatewaying multiple users.
>
> If there are bugs beyond what is documented, I'd love to hear about them.
>
> --
>    Bruce Campbell
>
>    Now, all I have to do is to complete my idea of having a corporate
>    gateway relaying from funkyname at subdept.corporate.example to
>    Proper.Name at corporate.example, and I'm set.
>


--
- Norman Rasmussen
 - Email: norman at rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/