[JDEV] client to client communication using jabber?

Dan vze2ry7c at verizon.net
Sat Jan 4 11:42:23 CST 2003

>From what I can gather from the specs it is also perfectly legal to send XML
payloads within the BODY element. Is this correct?

I am building a Jabber client for messaging business data. My clent will
know how to parse out and handle the elements packed in the body element.
The reason I would like package the data within the body element is so that
the data would not get lost if sent to a client that does not understand how
to handle a specialized x:namespace.

In testing with Winjab, when I receive data using a specialized namespace
there is no indication, except in the debux XML window, that anything came
in.  If put the data in the body tag it is displayed and available cfor
copying/pasting etc.

Is there any reason why I should not use the body element for packaging xml

----- Original Message -----
From: JD Conley <jconley at winfessor.com>
To: <jdev at jabber.org>
Sent: Friday, January 03, 2003 5:32 PM
Subject: RE: [JDEV] client to client communication using jabber?

> Sending XML Payloads with your messages is perfectly legal.  Just put it
> under the root message node like so.
> <message to='' from='' type='mycustommessage|chat|whatever'>
> <body>If you had my client you would be getting Bridge
> information.</body>
> <subject>bridge</subject>
> <mydata xmlns="my:custom:namespace">
> <bridgexml>
> more data
> </bridgexml>
> </mydata>
> </message>
> If you implement your own namespaces you aren't constrained by the
> jabber:x:x namespace specs (although jabber:x:oob is pretty open-ended).
> Also, it is not allowed to use a "jabber:mynamespace" namespace that
> isn't in the spec.
> Hope this helps.
> Regards,
> JD Conley
> Winfessor, Inc
> www.winfessor.com
> "Life would be so much easier if we could just see the source code."
> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org] On Behalf Of
> Pat Magnan
> Sent: Friday, January 03, 2003 2:07 PM
> To: jdev at jabber.org
> Subject: [JDEV] client to client communication using jabber?
> Brief description of what we're trying to do:
> - our project is a Bridge Bidding tool, it allows two players to
> 'practice'
> bidding hands over the Internet
> - we decided to use the JabberCom object, and use it for our embedded
> chat
> client (so they can discuss things from within the program)
> - when I saw I could send XML strings using Jabber, I thought I'd use
> that
> also for one client to talk to the other one (passing strings
> representing
> each player's hand of cards, what bid they're making, and so on).
> I'm having a little difficulty working out if it is even possible to
> send
> my own (somewhat limited) dtd or basically arbitrary data from one
> client/jid to the other (I don't care if it has to go through the
> server, I
> just want the server to forward it to the other client). Actual messages
> are no problem, but the documentation doesn't clearly guide me as to how
> to
> do that (much of it being in the form of proposals I guess so I'm trying
> to
> do things that aren't implemented it seems).
> I've seen things like jabber:x:data - which sounds like it would do, or
> jabber:something:oob. The protocol document was a good start, where do I
> go
> from here?
> The two clients can message successfully, so, it's a matter of working
> out
> how to send xml from one to the other (assuming I can) that contains my
> application's data.
> Any pointers or references that google isn't turning up for me that
> anyone
> can think of?
> Thanks,
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2715 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20030104/b370832a/attachment-0002.bin>

More information about the JDev mailing list