- From: Mark A. Jones <jones@research.att.com>
- Date: Tue, 19 Dec 2000 12:56:00 -0800
- To: xml-dist-app@w3.org
[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 Tuesday, 19 December 2000 15:55:43 UTC