W3C home > Mailing lists > Public > xml-dist-app@w3.org > May 2001

Re: xml transfer over TCP

From: Jean-Jacques Moreau <moreau@crf.canon.fr>
Date: Fri, 11 May 2001 11:54:34 +0200
Message-ID: <3AFBB6D9.1CBDAB0C@crf.canon.fr>
To: "John J. Barton" <John_Barton@hpl.hp.com>
CC: Lucas Gonze <lucas@worldos.com>, xml-dist-app@w3.org
From the first header line, you can see that messages are carried over (virtual)
channels, and that they can be framed. The RFC provides more details, as pointed
out earlier by Rich and Lucas.

Jean-Jacques.

"John J. Barton" wrote:

> In what way is this significantly different from HTTP?
> The only difference I see is the use of position rather
> than keywords for parameters, a giant leap backwards.
>
> John.
>
> At 11:55 AM 5/9/2001 +0200, Jean-Jacques Moreau wrote:
> >Lucas,
> >
> >I guess you've come across BEEP before?
> >   command SP channel SP msgno SP more SP seqno SP size CRLF
> >   [content type CRLF]
> >   CRLF
> >   XML data CRLF
> >   END
> >
> >Jean-Jacques.
> >
> >
> >
> >Lucas Gonze wrote:
> >
> > > I am looking for examples of XML protocols that do message transfer
> > over "plain"
> > > TCP, i.e. without an HTTP wrapper.  If you know something about the
> > formatting
> > > it would be very helpful.
> > >
> > > For example, a Goa protocol message as sent over TCP, and without HTTP, is:
> > > Goa CRLF
> > > byte count of XML data CRLF
> > > XML data
> > >
> > > Thanks in advance.
> > >
> > > - Lucas
>
> ______________________________________________________
> John J. Barton          email:  John_Barton@hpl.hp.com
> http://www.hpl.hp.com/personal/John_Barton/index.htm
> MS 1U-17  Hewlett-Packard Labs
> 1501 Page Mill Road              phone: (650)-236-2888
> Palo Alto CA  94304-1126         FAX:   (650)-857-5100
Received on Friday, 11 May 2001 05:55:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:01 GMT