Cart
[Home] [By Thread] [By Date] [Recent Entries]
David Megginson wrote: > More importantly, you don't want to have to parse an entire document > just to find out where it ends because that forces your system into > linear processing -- on a busy server, it is absolutely necessary to > be to isolate the documents/packets quickly and pass them off to > separate threads (or even separate boxes) for parsing and processing. Good point. I have been implicitly assuming this as a cost of moving the parsing function into the network infrastructure. However, a general-purpose endpoint implementation would have a hard time parallelizing in the way you describe because of possible inter-document dependencies in the application protocol. It has to deliver the documents to the next layer in the order in which they were sent. If parallelism is explicitly needed then a solution is to create multiple connections. xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
