XML over HTTP

[james anderson]

Greetings;

I have a simple question.

What are people doing when they read xml 'over the wire'?. It would appear
that the logical structure of an xml document (to wit
  [1] document ::= prolog element Misc*
) is at odds with the protocol specified for things like a http put operation.
For which a response from the recipient cannot come until after the operation
is performed. As a consequence of which, the input socket remain open (being a
two-way stream in order to write the response) after the object has been read.
In which case EOF is not a useful hint that the document is complete.

The same problem will appliy to connections which are kept alive for extended communications.

We could well assert a specific document structure, - for example prescribing
miscellaneous content after the document element, but i'm wondering what the
general W3 intent was.


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)