On 10/9/06, Pedro Melo <[EMAIL PROTECTED]> wrote:
> > does XCP useComponentBinding?
>
> Is this the Jabberd2.0 new protocolo for external componentes? If
> yes, then no. It does not.

Okay, the 'domains' parameter is only used if bind=true.  So it's not
required to change both instances.

> Basically, XCP (at least version 4) requires a static configuration
> on the router side. It requires an ID for each component, that
> combined with a realm gives you the link name that external
> components must use to connect (thats what we use compjid for in
> pymsnt and now in the yahoo-transport). The hostname setup is a
> different configuration entirely.
>
> So we need both: compjid for the name used in the initial <stream>
> handshake, and then hostname for the official name of the transport.

Sort of makes sense.

> > (trying to figure out if you need to change the compjid in the
> > domains part too)
> No. compjid is only used in the initial connection.

cool.

> BTW, compjid is a valid JID also, so you can assume that stanzas
> addressed to it are valid stanzas if you feel like it. It would be
> nice that you do so.
> <snip/>
> The reason to reply to compjid is related to monitoring and
> statistics. We use a XMPP-based bot that queries all our services
> using compjid to check out stats and availability. The ability to
> reply to an iq disco or jabber:iq:register or even ad-hoc commands
> over compjid is very useful in those situations, even if you only
> allow admin to use that address.

Making the compjid respond to iq's probably would be too hard, but I'd
prefer to limit it to disco and ad-hoc commands only, i.e. limited to
admin _functionality_ only.

-- 
- Norman Rasmussen
 - Email: [EMAIL PROTECTED]
 - Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED]  Mon Oct  9 12:24:29 2006
From: [EMAIL PROTECTED] (Michael Vogel)
Date: Mon Oct  9 12:24:44 2006
Subject: [py-transports] PyYIMt is disconnecting randomly
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Hi!

Norman Rasmussen schrieb:
> On 10/9/06, Michael Vogel <[EMAIL PROTECTED]> wrote:
>> Norman Rasmussen schrieb:
>> > I think this is the Yahoo network dropping the connection.
>>
>> Yeah I think this could be true. Yahoo isn't really stable and I don't
>> mean your transport ;-) When I was using the original client it
>> disconnects randomly as well.
>
> cool, so nothing has regressed :-)

Although the C-transport can deal better with this it. It seems to never
disconnects.

>> I do understand the problem. I think the transport should have some
>> reconnect option with a time out option. (Maybe reconnect only 10 times
>> then pause for several minutes and so on)
>
> Mmm, and if you log in with another yahoo client, then it should try at
> all :-)

My problem lies within Jabber clients that don't show the transports like
iChat. In iChat I can't log off/log on the transport. I know that iChat
isn't a very good jabber client - but it is looking cool so I'm using it
from time to time ;-)

Michael
-- 
"The Macintosh may only have 10% of the market,
but it is clearly the top 10%" - Douglas Adams 1952-2001

Reply via email to