- From: Andy Neilson <aneilson@webplan.com>
- Date: Wed, 20 Dec 2000 09:03:28 -0500
- To: "'Mark A. Jones'" <jones@research.att.com>, <xml-dist-app@w3.org>
I suspect this use case is fairly common. I have already done several implementations using this technique. I pointed out in an earlier message that the SOAP HTTP binding's use of HTTP status codes does not address this use case. This use case seems less associated with the sort of use we hear about most (i.e., RPC-oriented), and more associated more with document-oriented uses. Andy Neilson -----Original Message----- From: xml-dist-app-request@w3.org [mailto:xml-dist-app-request@w3.org]On Behalf Of Mark A. Jones Sent: Tuesday, December 19, 2000 15:56 To: xml-dist-app@w3.org Subject: use case [SAX-style XP handlers] [I have a series of use cases to add for the working group consideration. I am submitting one per message to allow for easier reference in the mail archives.] An XP sender generates a lengthy XP message that is incrementally transmitted and received by an XP receiver. The XP receiver employs an XP handler that can incrementally process the body as it is received (e.g., employing a SAX-style XML parser on the body as it arrives). Note that the entire message need not be present at one time at any point in its existence. This would be particularly helpful for memory-limited processors. It is also very efficient for services which are consistent with incremental, real-time transformations of the data, direct archiving of received data, etc. It would also be useful in scenarios in which voluminous body data can be directly transduced into application data structures or events by an XP (module) processor. In particular, there is no need for the explicit construction of a DOM model of the data. Support for XP data models might still be possible even with incremental processing if the models are incrementally constructible. -- Mark A. Jones AT&T Labs - Research Shannon Laboratory Room A201 180 Park Ave. Florham Park, NJ 07932-0971 email: jones@research.att.com phone: (973) 360-8326 fax: (973) 360-8970
Received on Wednesday, 20 December 2000 09:04:25 UTC