Hey There,
Ok. I've groked the situation of the XML Stream being it's own thing. Now, is
there a Schema or DTD for what an XML Stream is? It appears to me to be it's
own namespace at least...what are the valid attributes, etc?
--Ivan
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Thomas Charron
> Sent: Monday, May 21, 2001 6:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JDEV] Transport Decisions
>
>
> From: "Ivan R. Judson" <[EMAIL PROTECTED]>
> Subject: [JDEV] Transport Decisions
> > I'm delving deep into the jabber server architecture and the protocols.
> I'm
> > wondering however if there's a thread somewhere talking about the decision
> to
> > create the stream:stream namespace instead of using XML-RPC or SOAP?
>
> XML-RPC and SOAP use a variety of existing protocols as transports, and
> ride the actual XML payload on top of them. The stream namespace is
> basically strait XML over the socket. Don't think of it as a replacement
> for XML-RPC or SOAP. Think of it as just another transport. One could just
> as easily do XML-RPC and SOAP over the stream socket protocol.
>
> > I'm wondering if an evaluation of the merits has been done and if there's
> > anything I can read about that decision.
>
> See above. There are no socket streamed XML transports out there. the
> 'etherx scheme' provides this.
>
> _______________________________________________
> jdev mailing list
> [EMAIL PROTECTED]
> http://mailman.jabber.org/listinfo/jdev
>
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
