[jdev] Auto-configured external gateways

[Norman Rasmussen]

I was just looking into this for the yahoo-transport in the xmpp.py project, 

http://jabberd.jabberstudio.org/dev/docs/component.shtml

It seems that you need to bind to _all_ addresses you want to receive
traffic for.  I can only guess that in the current implementation, the
router automatically binds you to the component's address on
connection *shrug*

On 24/08/05, Daniel Henninger <jadestorm at nc.rr.com> wrote:
> Hi folk!
> 
> I'm trying to get a feel for exactly how a feature of jabberd2 and jive
> messenger works and am trying to figure out how to accomplish a specific
> task.  This is all regarding PyAIMt, so bear with me as I use aim as an
> example this whole time.
> 
> So jabberd1 and ejabberd both require me to pre-configure a transport that
> will be connecting to them.  For example, I would have to put in an entry
> for aim.jabber.foo.org, indicate which port they'll be talking to the
> transport through, and that sort of thing.
> 
> Jabberd2 and jive messenger, on the other hand, support "something" that
> enables the transport to connect and get auto-configured for lack of a
> better term.  I have since discovered with some help from the jdev
> conference room and my own sniffing that, upon connection, a service
> discovery request is sent to the transport and that's effectively how it
> figures out "what just connected to me?"... or at least that's my
> understanding.
> 
> So here's the issue.  PyAIM wants to be both aim.jabber.foo.org and
> chatrooms.aim.jabber.foo.org.  I'm hoping I don't have to make two
> entirely different connections to the serve to accomplish this.  Is it
> possible to indicate that I am both hosts?  I could certainly respond to
> the initial disco request with two different jid's worth of information,
> but my gut feeling is that the server will then ignore the jid that it
> wasn't asking about in the first place.  (ie: if it asks for aim.jabber
> and i respond with both aim.jabber and chatrooms.aim.jabber, it will only
> care about aim.jabber)  That may not be true.
> 
> So what's the proper way to do this and is there any documentation out
> there  that I could read that goes over this connect and service discovery
> mechanism?  Am I stuck with telling people they will need to configure the
> component manually?  I'm hoping not.  =)
> 
> Thanks for any help you all can provide!
> 
> Daniel
> 
> --
> "The most addictive drug in the world is music."
>      - The Lost Boyz
> 
> 
> 
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mail.jabber.org/mailman/listinfo/jdev
> 


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