[jdev] Unsubscribe please

Tue Feb 17 22:14:48 CST 2004

-----Mensaje original-----
De: jdev-bounces at jabber.org [mailto:jdev-bounces at jabber.org] En nombre
de jdev-request at jabber.org
Enviado el: Martes, 17 de Febrero de 2004 03:00 p.m.
Para: jdev at jabber.org
Asunto: jdev Digest, Vol 1, Issue 6

Send jdev mailing list submissions to
	jdev at jabber.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://jabberstudio.org/mailman/listinfo/jdev
or, via email, send a message with subject or body 'help' to
	jdev-request at jabber.org

You can reach the person managing the list at
	jdev-owner at jabber.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of jdev digest..."

Today's Topics:

   1. Empty <stream:features/> (Bob Phan)
   2. Re: Empty <stream:features/> (Robert Norris)
   3. Re: Empty <stream:features/> (Bob Phan)

----------------------------------------------------------------------

Message: 1
Date: Mon, 16 Feb 2004 16:42:36 -0500
From: Bob Phan <bob at devianttechnologies.com>
Subject: [jdev] Empty <stream:features/>
To: "jdev at jabber.org" <jdev at jabber.org>
Message-ID:
	<1076967756.26110.4.camel at eternity.devianttechnologies.com>
Content-Type: text/plain

Okay, a little progress update on the component library for perl for
jabber2.  It can now successfully authenticate using SASL and such. I
re-initiate the stream and the server returns this:

<stream:features xmlns:stream='http://etherx.jabber.org/streams'/>

Which most likely explains why when I try to bind to a domain, the
server debug output shows this:

ROUT: sx (io.c:189) decoded read data (33 bytes): <bind
name='logger'><log/></bind>
ROUT: sx (io.c:65) completed nad: <bind name='logger'><log/></bind>
ROUT: sx (chain.c:119) calling nad read chain
ROUT: sx (io.c:108) tag 12 event 6 data 0x80c1600
ROUT: Mon Feb 16 16:22:39 2004 router.c:736 invalid packet namespace,
dropping
ROUT: Mon Feb 16 16:22:42 2004 router.c:831 read action on fd 12

Since binding doesn't show up as a feature and all...

If anyone can shed any light on this problem, it would be very much
appreciated.

Thanks,

-- 
/*
 * Bob Phan <bob at devianttechnologies.com>
 * Code Master General
 * Deviant Technologies Incorporated
 * (203)458-2312
 *
 * http://www.devianttechnologies.com/
 */

------------------------------

Message: 2
Date: Tue, 17 Feb 2004 09:59:29 +1100
From: Robert Norris <rob at cataclysm.cx>
Subject: Re: [jdev] Empty <stream:features/>
To: Jabber software development list <jdev at jabber.org>
Message-ID: <20040216225929.GA587 at gideon.its.monash.edu.au>
Content-Type: text/plain; charset="us-ascii"

On Mon, Feb 16, 2004 at 04:42:36PM -0500, Bob Phan wrote:
> Okay, a little progress update on the component library for perl for 
> jabber2.  It can now successfully authenticate using SASL and such. I 
> re-initiate the stream and the server returns this:
> 
> <stream:features xmlns:stream='http://etherx.jabber.org/streams'/>
> 
> Which most likely explains why when I try to bind to a domain, the 
> server debug output shows this:
> 
> ROUT: sx (io.c:189) decoded read data (33 bytes): <bind 
> name='logger'><log/></bind>
> ROUT: sx (io.c:65) completed nad: <bind name='logger'><log/></bind>
> ROUT: sx (chain.c:119) calling nad read chain
> ROUT: sx (io.c:108) tag 12 event 6 data 0x80c1600
> ROUT: Mon Feb 16 16:22:39 2004 router.c:736 invalid packet namespace, 
> dropping
> ROUT: Mon Feb 16 16:22:42 2004 router.c:831 read action on fd 12
> 
> Since binding doesn't show up as a feature and all...

Component binding doesn't show up as a feature because it predates
stream features. Your problem stems from the (as the error messages say)
your packets being in the wrong namespace.

Either declare the component namespace on the stream header:

  <stream:stream xmlns:stream='http://etherx.jabber.org/streams'

xmlns='http://jabberd.jabberstudio.org/ns/component/1.0'>

Or on the packets themselves:

  <bind xmlns='http://jabberd.jabberstudio.org/ns/component/1.0'>
    <log/>
  </bind>

Take a look at the component protocol docs for more info. It may also
help to run a j2 component (the resolver is nice and simple) in debug
mode and watch the traffic that is passed back and forth.

Rob.

-- 
Robert Norris                                       GPG: 1024D/FC18E6C2
Email+Jabber: rob at cataclysm.cx                Web: http://cataclysm.cx/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url :
http://jabberstudio.org/pipermail/jdev/attachments/20040217/02f9734f/att
achment-0001.pgp

------------------------------

Message: 3
Date: Tue, 17 Feb 2004 12:52:23 -0500
From: Bob Phan <bob at devianttechnologies.com>
Subject: Re: [jdev] Empty <stream:features/>
To: Jabber software development list <jdev at jabber.org>
Message-ID:
	<1077040343.12708.16.camel at eternity.devianttechnologies.com>
Content-Type: text/plain

On Mon, 2004-02-16 at 17:59, Robert Norris wrote:
> On Mon, Feb 16, 2004 at 04:42:36PM -0500, Bob Phan wrote:
> > Okay, a little progress update on the component library for perl for

> > jabber2.  It can now successfully authenticate using SASL and such. 
> > I re-initiate the stream and the server returns this:
> > 
> > <stream:features xmlns:stream='http://etherx.jabber.org/streams'/>
> > 
> > Which most likely explains why when I try to bind to a domain, the 
> > server debug output shows this:
> > 
> > ROUT: sx (io.c:189) decoded read data (33 bytes): <bind 
> > name='logger'><log/></bind>
> > ROUT: sx (io.c:65) completed nad: <bind name='logger'><log/></bind>
> > ROUT: sx (chain.c:119) calling nad read chain
> > ROUT: sx (io.c:108) tag 12 event 6 data 0x80c1600
> > ROUT: Mon Feb 16 16:22:39 2004 router.c:736 invalid packet 
> > namespace, dropping
> > ROUT: Mon Feb 16 16:22:42 2004 router.c:831 read action on fd 12
> > 
> > Since binding doesn't show up as a feature and all...
> 
> Component binding doesn't show up as a feature because it predates 
> stream features. Your problem stems from the (as the error messages 
> say) your packets being in the wrong namespace.
> 
> Either declare the component namespace on the stream header:
> 
>   <stream:stream xmlns:stream='http://etherx.jabber.org/streams'
>                  
> xmlns='http://jabberd.jabberstudio.org/ns/component/1.0'>
> 
> Or on the packets themselves:
> 
>   <bind xmlns='http://jabberd.jabberstudio.org/ns/component/1.0'>
>     <log/>
>   </bind>
Thanks!  That was exactly the problem.  I didn't see any mention of that
namespace in the component doc you linked before.

> Take a look at the component protocol docs for more info. It may also 
> help to run a j2 component (the resolver is nice and simple) in debug 
> mode and watch the traffic that is passed back and forth.
Yes, that was very helpful.  I was looking for a component to mess
around with as an example before.

Thanks again for all your help.  I just finished up the library and
everything works now.  I sent a patch upstream to the maintainer, and
I'll shoot the list an email once it's been applied.

Now it's time to start work on the logging component.  I'll keep the
list informed on the progress of this component a little further down
the week.

Thanks again,
-- 
/*
 * Bob Phan <bob at devianttechnologies.com>
 * Code Master General
 * Deviant Technologies Incorporated
 * (203)458-2312
 *
 * http://www.devianttechnologies.com/
 */

------------------------------

_______________________________________________
jdev mailing list
jdev at jabber.org
https://jabberstudio.org/mailman/listinfo/jdev

End of jdev Digest, Vol 1, Issue 6
**********************************