[JDEV] dotgnu/jabber meetings, round 2
hi, all. back with another round of jabber/dotgnu meetings. the first one, http://dotgnu.org/pipermail/developers/2001-September/000998.html , was a great success. there will be 3 meetings, covering the same stuff for different people around the world. here are the rough times, please feedback if you'd like them changed. i'll work it out :) 7am Thursday UTC/GMT 7pm Thursday UTC/GMT 10pm Friday UTC/GMT at [EMAIL PROTECTED] i am taking feedback for an agenda. thanks :) -- /\ Adam Theo, Age 22, Tallahassee FL USA. //\\Theoretic Solutions (http://www.theoretic.com) //--\\ "Activism, Software, and Internet Services". ||Personal Homepage (http://www.theoretic.com/adamtheo). ||Jabber Platform (http://www.jabber.org). Birthright Online (http://www.birthright.net). Email & Jabber: [EMAIL PROTECTED] AIM: AdamTheo2000 ICQ: 3617306 Y!: AdamTheo2 "A patriotic American progressive buddhist with free-market socialist views" ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] Namespace usage on server
Hello, Writing my own client, I found something strange in the open source server : if I initiate the session with : fabrice everything works fine, but if I send : fabrice then the server sends me this error and closes the connection : Invalid Namespace I don't understand the rationale of this error message. My first XML stream is perfectly valid and the QName of the elements are the same in both cases. I didn't find any mention of this requirement in the docs so I guess it's a bug in the server ? Fabrice -- Fabrice Desré - France Telecom R&D/DMI/GRI Tel: +(33) 2 96 05 31 43 Fax: +(33) 2 96 05 32 86 ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
> xmlns:stream='http://etherx.jabber.org/streams' >xmlns='jabber:client'> > vs. > xmlns:stream='http://etherx.jabber.org/streams'> > The xmlns 'jabber:client' refers to the stream, not just any old element (e.g., your element) within the stream, thus the error. All streams must be identified as jabber:client, jabber:component, or jabber:server. Now, granted this is perhaps not well documented, but it's not a bug in the server. Here's a copy of the DTD: http://www.saint-andre.com/jabber/dtds/streams.dtd.txt Peter ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
hi, no, there is nothing strange in this error. when initiating a client connection to a jabber server, the root xml must specify the namespace (here, xmlns='jabber:client'). specifying the namespace in the iq request is not valid. the client connection manager (pthsock for instance) just looks at the root xml ... regards, Benoit. -- Benoit Orihuela IDEALX S.A.S. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
Actually, what you are seeing is broken behaviour in Jabber's handling of namespaces. In keeping with the XML 1.0 and XML Namespaces spec, specifying the namespace on a per packet basis is perfectly acceptable. Unfortunately, up to this point, the Jabber server doesn't process namespaces at all (at least, in a correct manner) and hence you get unexpected behaviour when you move the namespace declarations around. At some point, someone will have to fix this.. :) Diz On Wed, Oct 03, 2001 at 03:16:25PM +0200, Fabrice DESRE - FT.BD/FTRD/DMI/GRI wrote: > Hello, > > Writing my own client, I found something > strange in the open source server : if I > initiate the session with : > > xmlns:stream='http://etherx.jabber.org/streams' >xmlns='jabber:client'> > > > fabrice > > > > > everything works fine, but if I send : > > > xmlns:stream='http://etherx.jabber.org/streams'> > > > fabrice > > > > > then the server sends me this error and closes the connection : > > id='3BBB0DE3' > xmlns='jabber:client' > from='jabber'> >Invalid Namespace > > > I don't understand the rationale of this error message. My first XML > stream is perfectly valid and the QName of the elements are the same > in both cases. > I didn't find any mention of this requirement in the docs so I guess > it's a bug in the server ? > > Fabrice > -- > Fabrice Desr? - France Telecom R&D/DMI/GRI > Tel: +(33) 2 96 05 31 43 > Fax: +(33) 2 96 05 32 86 > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
Benoit Orihuela wrote: > > when initiating a client connection to a jabber server, the root xml > must specify the namespace (here, xmlns='jabber:client'). > specifying the namespace in the iq request is not valid. Why is it not valid ? Does jabber ues a special flavour of XML ? Regards, Fabrice -- Fabrice Desré - France Telecom R&D/DMI/GRI Tel: +(33) 2 96 05 31 43 Fax: +(33) 2 96 05 32 86 ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
hi, > Why is it not valid ? Does jabber ues a special flavour of XML ? just take a look at the DTDs on the stpeter's site : http://www.saint-andre.com/jabber/dtds/ (the stream must contain an xmlns attribute and iq can only contain to, from, id and type attributes.) regards, Benoit. -- Benoit Orihuela IDEALX S.A.S. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
Two things: 1) the 'to' attribute (as well as the 'id' attribute) are part of the jabber:client namespace. 2) namespaces are not used correctly by the server - while the resulting stream is well-formed XML and does use namespaces correctly, there is no flexibility on *how* you use those namespaces. For instance, if you started the stream off with instead of , it would have also broken. - David Waite Fabrice DESRE - FT.BD/FTRD/DMI/GRI wrote: > Hello, > > Writing my own client, I found something >strange in the open source server : if I >initiate the session with : > > xmlns:stream='http://etherx.jabber.org/streams' > xmlns='jabber:client'> > > > fabrice > > > > > everything works fine, but if I send : > > > xmlns:stream='http://etherx.jabber.org/streams'> > > > fabrice > > > > >then the server sends me this error and closes the connection : > >id='3BBB0DE3' >xmlns='jabber:client' >from='jabber'> > Invalid Namespace > > > I don't understand the rationale of this error message. My first XML >stream is perfectly valid and the QName of the elements are the same >in both cases. >I didn't find any mention of this requirement in the docs so I guess >it's a bug in the server ? > > Fabrice > ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
Benoit Orihuela wrote: >hi, > >> Why is it not valid ? Does jabber ues a special flavour of XML ? >> >just take a look at the DTDs on the stpeter's site : >http://www.saint-andre.com/jabber/dtds/ >(the stream must contain an xmlns attribute and iq can only contain >to, from, id and type attributes.) > >regards, > >Benoit. > xmlns is not a valid attribute in a DTD - it is a reserved attribute name, which is normally used for specifying namespaces. -David Waite ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
Peter Saint-Andre wrote: > The xmlns 'jabber:client' refers to the stream, not just any old element > (e.g., your element) within the stream, thus the error. All streams > must be identified as jabber:client, jabber:component, or jabber:server. > Now, granted this is perhaps not well documented, but it's not a bug in > the server. I understand your logic here about tbe necessity to differenciate stream types, but the use of a default namespace declaration for this is IMHO a bad choice. Why not use a real attribute ? Namespace declarations are very different from attributes when you consider the XML data model. That's why I found it incorrect, and at least disturbing. Any parser namespace-compliant parser will tell you that my two previous example made no difference with respect to the QNames of elements. But looking quickly at libxode, it doesn't seem to really support namespaces. > Here's a copy of the DTD: > http://www.saint-andre.com/jabber/dtds/streams.dtd.txt You know that DTD are not able to cope with namespaces, so it is not really a valid point. You should try to write XML Schemas for jabber to get rid of this kind of ambiguity. Regards, Fabrice -- Fabrice Desré - France Telecom R&D/DMI/GRI Tel: +(33) 2 96 05 31 43 Fax: +(33) 2 96 05 32 86 ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
David Waite wrote: > > Two things: > > 1) the 'to' attribute (as well as the 'id' attribute) are part of the > jabber:client namespace. No. Attributes must explicitly specify namespaces. They don't inherit from the default namespace (see §5.2 of http://www.w3.org/TR/REC-xml-names/). > 2) namespaces are not used correctly by the server - while the resulting > stream is well-formed XML and does use namespaces correctly, there is no > flexibility on *how* you use those namespaces. For instance, if you > started the stream off with instead of , > it would have also broken. From the response of P.Saint Andre, I also think that sadly they are used in a bad way. Regards, Fabrice -- Fabrice Desré - France Telecom R&D/DMI/GRI Tel: +(33) 2 96 05 31 43 Fax: +(33) 2 96 05 32 86 ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
> > Here's a copy of the DTD: > > http://www.saint-andre.com/jabber/dtds/streams.dtd.txt > > You know that DTD are not able to cope with namespaces, so it is not > really a valid point. You should try to write XML Schemas for jabber > to get rid of this kind of ambiguity. Definitely. They're in the works. Peter ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] forms
Hello, IMO, the forms JEP are incredibly simplistic. I honestly don't see how one could build a decent form (I mean the layout) with the scheme you suggested, only a long list of input fields/boxes/etc. Why shouldn't Jabber use XHTML/CSS to display forms? That way it fits into Jabber's XML tags and we can guarantee forms will look (almost) identical on every user's display. btw, why don't you include an editable pull-down box in the JEP? (I wish they had put them into the HTML spec!) Oh, I think you left out file-selection boxes ... those can be quite useful. Bye, Sebastiaan - Original Message - From: "Peter Saint-Andre" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, October 02, 2001 5:48 PM Subject: [JDEV] forms > As I was taking notes at JabberCon, one theme that kept popping into my > mind was the need for strong forms support in Jabber. Just as the World > Wide Web consisted mostly of reading hyperlinked documents (albeit > eventually with some flashy graphics and multimedia stuff) until web > developers figured out how to offer interactive forms and therefore > "weblications" like searching the web and ordering books online, so I > think Jabber will consist mostly of IM (and a few related applications) > until we have Jabber forms that will enable developers to create more > robust "Jablications" like ___ (you fill in the blank :). > > I don't have any answers or specific proposals to offer, but I'd certainly > like to get the discussion going. Ryan Eatmon put together a proposed spec > for Jabber forms a number of months ago, and even converted it into JEP > format, but there's been minimal discussion of it and I think that's what > we need to move forward. The JEP can be found here: > > http://foundation.jabber.org/jeps/jep-0004.html > > More specifically, I'm wondering if there is value in looking at the W3C > spec for XForms. Here are some links of interest for that angle: > > http://www.xml.com/lpt/a/2001/09/05/xforms.html > http://www.xml.com/lpt/a/2001/09/26/xforms.html > http://www.w3.org/TR/2001/WD-xforms-20010828/ > > There are 12 people on the forms-jig mailing list and 1050 people on the > JDEV list. I invite those of you who are interested in building more > advanced data interchange over Jabber (as opposed to simple IM) to join > the forms-jig list so we can kick-start this discussion: > > http://mailman.jabber.org/listinfo/forms-jig/ ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] forms
On Wed, Oct 03, 2001 at 05:54:46PM +0200, Sebastiaan 'CBAS' Deckers wrote: > Hello, > > IMO, the forms JEP are incredibly simplistic. > I honestly don't see how one could build a decent form (I mean the layout) > with the scheme you suggested, only a long list of input fields/boxes/etc. > Why shouldn't Jabber use XHTML/CSS to display forms? That way it fits into > Jabber's XML tags and we can guarantee forms will look (almost) identical on > every user's display. > > btw, why don't you include an editable pull-down box in the JEP? (I wish > they had put them into the HTML spec!) > Oh, I think you left out file-selection boxes ... those can be quite useful. Hi It may be worth having a word with the folks on the forms JIG the info for the mailing list was in Peter's post, or can be got from the http://dev.jabber.org page. All discussion contributions gratefully accepted :-) dj ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] forms
That's why we have the forms-jig, to hash these issues out. :) On Wed, 3 Oct 2001, Sebastiaan 'CBAS' Deckers wrote: > Hello, > > IMO, the forms JEP are incredibly simplistic. > I honestly don't see how one could build a decent form (I mean the layout) > with the scheme you suggested, only a long list of input fields/boxes/etc. > Why shouldn't Jabber use XHTML/CSS to display forms? That way it fits into > Jabber's XML tags and we can guarantee forms will look (almost) identical on > every user's display. > > btw, why don't you include an editable pull-down box in the JEP? (I wish > they had put them into the HTML spec!) > Oh, I think you left out file-selection boxes ... those can be quite useful. > > Bye, > Sebastiaan > > - Original Message - > From: "Peter Saint-Andre" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, October 02, 2001 5:48 PM > Subject: [JDEV] forms > > > > As I was taking notes at JabberCon, one theme that kept popping into my > > mind was the need for strong forms support in Jabber. Just as the World > > Wide Web consisted mostly of reading hyperlinked documents (albeit > > eventually with some flashy graphics and multimedia stuff) until web > > developers figured out how to offer interactive forms and therefore > > "weblications" like searching the web and ordering books online, so I > > think Jabber will consist mostly of IM (and a few related applications) > > until we have Jabber forms that will enable developers to create more > > robust "Jablications" like ___ (you fill in the blank :). > > > > I don't have any answers or specific proposals to offer, but I'd certainly > > like to get the discussion going. Ryan Eatmon put together a proposed spec > > for Jabber forms a number of months ago, and even converted it into JEP > > format, but there's been minimal discussion of it and I think that's what > > we need to move forward. The JEP can be found here: > > > > http://foundation.jabber.org/jeps/jep-0004.html > > > > More specifically, I'm wondering if there is value in looking at the W3C > > spec for XForms. Here are some links of interest for that angle: > > > > http://www.xml.com/lpt/a/2001/09/05/xforms.html > > http://www.xml.com/lpt/a/2001/09/26/xforms.html > > http://www.w3.org/TR/2001/WD-xforms-20010828/ > > > > There are 12 people on the forms-jig mailing list and 1050 people on the > > JDEV list. I invite those of you who are interested in building more > > advanced data interchange over Jabber (as opposed to simple IM) to join > > the forms-jig list so we can kick-start this discussion: > > > > http://mailman.jabber.org/listinfo/forms-jig/ > > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] More on namespaces in jabberd
Hello, Just another misbehavior in jabberd : If I send: fabrice This should be correctly understood by jabberd, but it is not the case :-(( (I get a 406 error 'not acceptable') It seems simply that jabberd is not namespace aware, hence it is not conformant with the standards it claims to use. Being stuck with UTF-8 is an acceptable constraint (ok with respect to the standard) but a so inaccurate support of namespaces is not. Are there any plans to a) upgrade libxode or b) switch to a conformant parser (xerces in sax2 mode comes to mind) ? Regards, Fabrice -- Fabrice Desré - France Telecom R&D/DMI/GRI Tel: +(33) 2 96 05 31 43 Fax: +(33) 2 96 05 32 86 ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
Diz is right, we just need to make our parser in the next gen reference implementation (and possibly a patch for 1.4.x) to fully understand namespaces. The rest of this thread seems like a bit of miscommunication or crossed wires. Let's fix this rather than argue over it, we've identitified the problem. --temas On Wed, 2001-10-03 at 09:05, Dave Smith wrote: > Actually, what you are seeing is broken behaviour in Jabber's handling > of namespaces. In keeping with the XML 1.0 and XML Namespaces spec, > specifying the namespace on a per packet basis is perfectly acceptable. > Unfortunately, up to this point, the Jabber server doesn't process > namespaces at all (at least, in a correct manner) and hence you get > unexpected behaviour when you move the namespace declarations around. > > At some point, someone will have to fix this.. :) > > Diz > > > On Wed, Oct 03, 2001 at 03:16:25PM +0200, Fabrice DESRE - FT.BD/FTRD/DMI/GRI wrote: > > Hello, > > > > Writing my own client, I found something > > strange in the open source server : if I > > initiate the session with : > > > > >xmlns:stream='http://etherx.jabber.org/streams' > >xmlns='jabber:client'> > > > > > > fabrice > > > > > > > > > > everything works fine, but if I send : > > > > > > >xmlns:stream='http://etherx.jabber.org/streams'> > > > > > > fabrice > > > > > > > > > > then the server sends me this error and closes the connection : > > > > > id='3BBB0DE3' > > xmlns='jabber:client' > > from='jabber'> > >Invalid Namespace > > > > > > I don't understand the rationale of this error message. My first XML > > stream is perfectly valid and the QName of the elements are the same > > in both cases. > > I didn't find any mention of this requirement in the docs so I guess > > it's a bug in the server ? > > > > Fabrice > > -- > > Fabrice Desr? - France Telecom R&D/DMI/GRI > > Tel: +(33) 2 96 05 31 43 > > Fax: +(33) 2 96 05 32 86 > > ___ > > jdev mailing list > > [EMAIL PROTECTED] > > http://mailman.jabber.org/listinfo/jdev > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev PGP signature
Re: [JDEV] Namespace usage on server
temas wrote: > > Diz is right, we just need to make our parser in the next gen reference > implementation (and possibly a patch for 1.4.x) to fully understand > namespaces. The rest of this thread seems like a bit of > miscommunication or crossed wires. Let's fix this rather than argue > over it, we've identitified the problem. I think that more than a namespace conformance issue, this can potentially raise a design issue - I'm referring here to the default namespace declaration in being used as a way to identify the class of the stream. Perhaps using a different stream namespace for each case could solve this problem in more efficient and conform way. Regards, Fabrice -- Fabrice Desré - France Telecom R&D/DMI/GRI Tel: +(33) 2 96 05 31 43 Fax: +(33) 2 96 05 32 86 ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] Jabber Success story
Hi Everyone, I recently presented a paper at the Erlang User conference about a product using jabber. The product was developed using a front end in Erlang/OTP, a distributed functional programming language originally developed by Ericsson to program switches, but recently (after having become Open Source), also used in other areas, among them, products for ISPs. (mail robustifiers, web servers, ssl off loaders, etc.). You can find the paper and the slides at http://www.erlang-consulting.com/euc2001/index.htm Hope you enjoy it, and feel free to email me or Mickael questions. (Note, however, that I am not on the mailing list). Regards, Francesco -- http://www.erlang-consulting.com begin:vcard n:Cesarini;Francesco tel;cell:0044 (0) 7776 250 381 tel;fax:0044 (0)870 1390 779 x-mozilla-html:FALSE url:http://www.erlang-consulting.com org:Cesarini Consulting Ltd. adr:;;26 May Road;Twickenham;;TW2 6QP;United Kingdom version:2.1 email;internet:[EMAIL PROTECTED] title:Technical Consultant fn:Francesco Cesarini end:vcard
Re: [JDEV] Namespace usage on server
Yeah, that's probably not cool currently, and I don't know how to quickly fix all the servers installed. With the next gen work it can probably be taken care of to understand the namespacing better. Jer, any thoughts on potential fixes for the current system? --temas On Wed, 2001-10-03 at 11:59, Fabrice DESRE - FT.BD/FTRD/DMI/GRI wrote: > temas wrote: > > > > Diz is right, we just need to make our parser in the next gen reference > > implementation (and possibly a patch for 1.4.x) to fully understand > > namespaces. The rest of this thread seems like a bit of > > miscommunication or crossed wires. Let's fix this rather than argue > > over it, we've identitified the problem. > > I think that more than a namespace conformance issue, this can > potentially > raise a design issue - I'm referring here to the default namespace > declaration > in being used as a way to identify the class of the > stream. > Perhaps using a different stream namespace for each case could solve > this > problem in more efficient and conform way. > > Regards, > > Fabrice > PGP signature
[JDEV] unicode client in java
Hi everyone, I'm developping a java client for jabber but sometimes it disconnects. I discovered that it was because I don't support unicode ... how can I arrange this? ( or support it ) in java? Thanks in advance. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] forms
Another standard that might be considered for this is XUL. >From: DJ Adams <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: Re: [JDEV] forms >Date: Wed, 3 Oct 2001 17:10:59 +0100 > >On Wed, Oct 03, 2001 at 05:54:46PM +0200, Sebastiaan 'CBAS' Deckers wrote: > > Hello, > > > > IMO, the forms JEP are incredibly simplistic. > > I honestly don't see how one could build a decent form (I mean the >layout) > > with the scheme you suggested, only a long list of input >fields/boxes/etc. > > Why shouldn't Jabber use XHTML/CSS to display forms? That way it fits >into > > Jabber's XML tags and we can guarantee forms will look (almost) >identical on > > every user's display. > > > > btw, why don't you include an editable pull-down box in the JEP? (I wish > > they had put them into the HTML spec!) > > Oh, I think you left out file-selection boxes ... those can be quite >useful. > >Hi > >It may be worth having a word with the folks on the forms JIG >the info for the mailing list was in Peter's post, or can be >got from the http://dev.jabber.org page. > >All discussion contributions gratefully accepted :-) > >dj >___ >jdev mailing list >[EMAIL PROTECTED] >http://mailman.jabber.org/listinfo/jdev _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] jserve 0.1a uploaded
just a quick note, i released the first 0.1 version of jserve, a jabber-server in python. it's very alpha, very featureless but illustrates how the server should work. Daniel T. Bender http://sourceforge.net/projects/jserve ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] More on namespaces in jabberd
Again, due to the fact that _none_ of the current Jabber source handles namespaces properly, nothing using namespaces like this will work.. This is a rather large fix to effect -- it requires a lot of code to be examined to deal with namespaces when processing packets. At this point, it's probably easiest to just start handling these issues in the jabelin implementation. Diz On Wed, Oct 03, 2001 at 06:13:26PM +0200, Fabrice DESRE - FT.BD/FTRD/DMI/GRI wrote: > Hello, > > Just another misbehavior in jabberd : > If I send: > > xmlns:stream='http://etherx.jabber.org/streams' > xmlns='jabber:client' > xmlns:jab='jabber:client'> > > > fabrice > > > > > This should be correctly understood by jabberd, but it is not > the case :-(( (I get a 406 error 'not acceptable') > It seems simply that jabberd is not namespace aware, hence it is > not conformant with the standards it claims to use. Being stuck > with UTF-8 is an acceptable constraint (ok with respect to the > standard) but a so inaccurate support of namespaces is not. > Are there any plans to a) upgrade libxode or b) switch to a > conformant parser (xerces in sax2 mode comes to mind) ? > > Regards, > > Fabrice > -- > Fabrice Desr? - France Telecom R&D/DMI/GRI > Tel: +(33) 2 96 05 31 43 > Fax: +(33) 2 96 05 32 86 > ___ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] More on namespaces in jabberd
> It seems simply that jabberd is not namespace aware, hence it is > not conformant with the standards it claims to use. Not true, it's use is conformant with namespaces, it is only using a subset of the specification in this case. This is no different from the use of XML, in that there is no support for entities, prologs, etc, and only a subset of XML is actually being used. Other than the namespaces the server uses itself, all other uses (between clients, services, or any software sending xml via jabber) may use namespaces in any way they choose. > Being stuck > with UTF-8 is an acceptable constraint (ok with respect to the > standard) but a so inaccurate support of namespaces is not. > Are there any plans to a) upgrade libxode or b) switch to a > conformant parser (xerces in sax2 mode comes to mind) ? There are no plans for this type of overhaul for the 1.4 codebase as most of the server development effort is being put into jabelin. At this point a server supporting namespaces in such a way would have to translate all namespace usage into the current "flat" format for existing clients and servers it delivers to, supporting the feature in this way would offer no benefit to anyone other than the sender. I do agree that it would be very nice and we should work towards a new rev of the protocol specification in the future that encourages using namespaces more broadly (after we get the current one well defined of course). Jer ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Namespace usage on server
Fabrice DESRE - FT.BD/FTRD/DMI/GRI wrote: [EMAIL PROTECTED]"> David Waite wrote: Two things:1) the 'to' attribute (as well as the 'id' attribute) are part of thejabber:client namespace. No. Attributes must explicitly specify namespaces. They don't inheritfrom the default namespace (see §5.2 ofhttp://www.w3.org/TR/REC-xml-names/). Argh, you are right (and reminded me why I hate XML namespaces so much). There is no way for an attribute to reference the default namespace URI within a qualified element; you have to define a new namespace prefix pointing to the same URI in order to pull it off. -David Waite
Re: [JDEV] More on namespaces in jabberd
well put :-) I would like to know reasons that this is not considered acceptable - I have plenty of points against it in my mind in the way of backwards compatiblity and server workload, but no solid points for it. -David Waite Jeremie wrote: >>It seems simply that jabberd is not namespace aware, hence it is >>not conformant with the standards it claims to use. >> > >Not true, it's use is conformant with namespaces, it is only using a >subset of the specification in this case. This is no different from the >use of XML, in that there is no support for entities, prologs, etc, and >only a subset of XML is actually being used. Other than the namespaces >the server uses itself, all other uses (between clients, services, or any >software sending xml via jabber) may use namespaces in any way they >choose. > >>Being stuck >>with UTF-8 is an acceptable constraint (ok with respect to the >>standard) but a so inaccurate support of namespaces is not. >> Are there any plans to a) upgrade libxode or b) switch to a >>conformant parser (xerces in sax2 mode comes to mind) ? >> > >There are no plans for this type of overhaul for the 1.4 codebase as most >of the server development effort is being put into jabelin. At this point >a server supporting namespaces in such a way would have to translate all >namespace usage into the current "flat" format for existing clients and >servers it delivers to, supporting the feature in this way would offer >no benefit to anyone other than the sender. > >I do agree that it would be very nice and we should work towards a new rev >of the protocol specification in the future that encourages using >namespaces more broadly (after we get the current one well defined of >course). > >Jer > >___ >jdev mailing list >[EMAIL PROTECTED] >http://mailman.jabber.org/listinfo/jdev > ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] unicode client in java
David Rainville wrote: >Hi everyone, >I'm developping a java client for jabber but sometimes it disconnects. I >discovered that it was because I don't support unicode ... how can I arrange >this? ( or support it ) in java? > >Thanks in advance. > > > >___ >jdev mailing list >[EMAIL PROTECTED] >http://mailman.jabber.org/listinfo/jdev > Java itself has UCS2 characters as the native character type. Are you sending text to the server in UTF-8 encoding? -David Waite ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] phenomenon associated with frequent connections
Hello all.
I'm hoping you can help explain the following phenomenon. I'm guessing that
it's well-understood
and easily explained.
Consider this (admittedly pathological) test program:
for ( i = 1 to 10 ) {
connect to Jabber server;
authenticate;
pull roster information;
disconnect from Jabber server;
sleep; (optional)
}
If I do not put the thread to sleep at the bottom of the loop, I run into
trouble on
the sixth iteration -- and the trouble seems to arise consistently on the
sixth iteration. What
actually happens is that on the sixth pass, I am able to establish a socket
connection,
but as soon as I send an authentication packet, the server sends a TCP FIN
segment
indicating that it's not going to interact with me anymore. After a few
seconds, everything
is back to normal.
If on the other hand I put the thread to sleep for a period of time -- a
few seconds or so --
I never encounter problems; I can connect and disconnect as often as I wish.
Any ideas? I'm using, I belive, version 1.4 hosted on Solaris.
Thanks, Charles.
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] phenomenon associated with frequent connections
On Wed, Oct 03, 2001 at 09:40:31PM -0700, Charles Owen wrote:
> Hello all.
>
> Consider this (admittedly pathological) test program:
>
> for ( i = 1 to 10 ) {
> connect to Jabber server;
> authenticate;
> pull roster information;
> disconnect from Jabber server;
> sleep; (optional)
> }
>
> If I do not put the thread to sleep at the bottom of the loop, I run into
> trouble on
> the sixth iteration -- and the trouble seems to arise consistently on the
> sixth iteration. What
> actually happens is that on the sixth pass, I am able to establish a socket
> connection,
> but as soon as I send an authentication packet, the server sends a TCP FIN
> segment
> indicating that it's not going to interact with me anymore. After a few
This sounds very much like the rate limiting mechanism kicking in.
The directive in the configuration (jabber.xml) allows the
server admin to throttle the rate of connection on a socket. I think
the default might even look like this:
which says throttle the socket if more than 5 connection attempts are
made in 25 seconds. The throttle is relaxed after that 25 second period.
dj
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] More on namespaces in jabberd
Jeremie wrote: > > > Not true, it's use is conformant with namespaces, it is only using a > subset of the specification in this case. This is no different from the > use of XML, in that there is no support for entities, prologs, etc, and > only a subset of XML is actually being used. Other than the namespaces > the server uses itself, all other uses (between clients, services, or any > software sending xml via jabber) may use namespaces in any way they > choose. Using a subset of XML can be really annoying. Think about the lack of entities when sending XHTML docs for instance... By the way, can you point me to a doc where I can find these limitations ? What i'm saying is the current implementation of jabberd (1.4) is broken with respect to namespaces. My first post in this thread demonstrates this : the server can't process correctly this valid stream. If you use a non compliant parser for your XML application, you're very likely to go into troubles. > I do agree that it would be very nice and we should work towards a new rev > of the protocol specification in the future that encourages using > namespaces more broadly (after we get the current one well defined of > course). I agree with you on that. Good namespaces usage (ie at design stage) is not always easy, but you can get lots of benefits from it. Some area of improvement I can see right now : - re-think the namespaces - re-think the element Fabrice -- Fabrice Desré - France Telecom R&D/DMI/GRI Tel: +(33) 2 96 05 31 43 Fax: +(33) 2 96 05 32 86 ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
