XMLP-UC-6 reformulation - simple streaming use case

Hi all, as per my action item I hereby propose a reformulation of the
XMLP-UC-6 [1] use case generated during the face-to-face.

The use-case is a major "rat-hole" that we want to tiptoe carefully
around, therefore what I'm proposing is a very constrained but still
useful version of the usecase.

-------- Simple streaming use case begin

An application wants to send one big (but limited) piece of binary data
from the sender to the receiver. Either of the parties is limited so it
needs to be able to produce/consume the data in a streaming fashion,
i.e. the SOAP Envelope must be available with only the streamed binary
data being in process of transmission.

-------- end

I'm trying to convey that we ought to make possible (if only in our
concrete binding, not in the abstract layer) the case where an
application only has one "attachment" and wants to stream it. This use
case is not concerned with cases of multiple "attachments", one or more
of which might be streamed. Nor is this use case concerned with
potentially unlimited sources of data like sensor readings or radio
audio streams.

Hope it's acceptable 8-)

                   Jacek Kopecky

                   Senior Architect
                   Systinet Corporation
                   http://www.systinet.com/




[1] burried in http://www.w3.org/2000/xp/Group/3/03/06-minutes.html

Received on Wednesday, 17 September 2003 13:37:31 UTC