W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2003

RE: AFTF requirements, pre-2003/01/31 telcon

From: David Orchard <dorchard@bea.com>
Date: Mon, 3 Feb 2003 19:01:01 -0800
To: "'Rich Salz'" <rsalz@datapower.com>, "'John J. Barton'" <John_Barton@hpl.hp.com>
Cc: "'Martin Gudgin'" <mgudgin@microsoft.com>, <noah_mendelsohn@us.ibm.com>, <jones@research.att.com>, "'Sanjiva Weerawarana'" <sanjiva@watson.ibm.com>, <xml-dist-app@w3.org>
Message-ID: <011201c2cbf9$a6f5d860$c30ba8c0@beasys.com>

I did mention chunking in an earlier requirements posting.  That is one type
of streaming.

Cheers,
Dave

> -----Original Message-----
> From: xml-dist-app-request@w3.org
> [mailto:xml-dist-app-request@w3.org]On
> Behalf Of Rich Salz
> Sent: Monday, February 03, 2003 6:52 PM
> To: John J. Barton
> Cc: Martin Gudgin; noah_mendelsohn@us.ibm.com; jones@research.att.com;
> Sanjiva Weerawarana; xml-dist-app@w3.org
> Subject: RE: AFTF requirements, pre-2003/01/31 telcon
>
>
>
> > Ok, so now I am complete confused.  The likely outcome from the AFTF
> > effort would be a specification that would lead to a
> software component
> > in a SOAP engine preceding XML parsing.  The component would pull
> > bits off the wire and prepare them for application level processing.
>
> I hope it's not going to be required that ALL bits be pulled
> off the wire
> before being processed. I'd like to use SOAP with streaming media.
> (I think that also argues against the Infoset proposal.)
>         /r$
>
Received on Monday, 3 February 2003 22:04:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:13 GMT