Re: New Attachments Issues

As we're only talking about optimization of transfer of binary data
(we're not yet talking about the other aspects of PASWA, like
swa:Representation), it is not critical from our point of view that the
optimization be preserved across intermediaries (1) or that it be done
at all (2). However, I do think we should say something, so I prefer
option (ii) below - that we say your two questions are answered in
implementations in an implementation-specific way.

It is important that whatever we produce from PASWA emphasizes the fact
that we're providing a possible optimization of binary data transfer and
how it may be particularly useful with the other stuff like
swa:Representation.

Best regards,

                   Jacek Kopecky

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





On Fri, 2003-06-06 at 18:25, Marc Hadley wrote:
> All,
> 
> Following the resolution of issue 429[1], I'd like to raise the 
> following new issues:
> 
> 1: "What are the semantics of attachments w.r.t. SOAP intermediaries. 
> E.g. do we expect intermediaries to preserve what is serialized as 
> attachments and what is serialized inside the SOAP envelope."
> 
> 2: "How does the binding determine which nodes to serialize as 
> attachments ?"
> 
> Amongst the many possible answers, the following spring immediately to 
> mind:
> 
> (i) We don't specify that.
> (ii) An implementation specific mechanism (similar to (i) but we 
> explicitly say so).
> (iii) Its triggered by something in the infoset - if so, what.
> 
> Thanks,
> Marc.
> 
> [1] http://www.w3.org/2000/xp/Group/xmlp-issues#x429
> 
> --
> Marc Hadley <marc.hadley@sun.com>
> Web Technologies and Standards, Sun Microsystems.

Received on Tuesday, 10 June 2003 07:46:54 UTC