- Original Message -
From: "Daniel Veillard" <[EMAIL PROTECTED]>
[stuff munched]
> I implemented XML-RPC on top of Jabber (following the draft from last
summer)
> and it's actually very nice to be able to parse all the XML-RPC calls of
the
> application with the same parser instance, nea
On Fri, Jan 04, 2002 at 04:41:39PM -0800, zak wrote:
> for example, instead of sending this...
>
>xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'>
>
> doesn't it make sense to send...
>
>xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'>
>
The session is set up as a continuous Jabber document for correct and
efficient namespace handling. You will notice in the stream:stream tag that
a default namespace jabber:client is specified. Since all the message, iq,
and presence elements are children of this document, they adopt this
default
(I apologize if this comes late, I receive the "digest" rather than being
swamped with e-mails...)
I'm mostly guessing here, but I believe the reason for a "running" XML
document is for the implicit connection status this provides. If the
document is still open (and there hasn't been an ungracef
