Re: WSDL binding for DIME

Hi,

Makes sense, I figured it was to assist streaming implementations.

I only mention it since it introduces a linkage between the composition =
of the SOAP message and the assembly of the DIME package, which might be =
problematic if these tasks are done by different pieces of code in an =
implementation.

At the moment I'm fine with it, as the (soon to be announced) =
implementation here happens to allow the app code generating the SOAP =
message to control the order of attachments anyway.

Anyway, it's nice to have a WSDL binding for DIME.

RC

1) This is to support implementations that use streaming APIs like SAX
and XmlReader. Such implementations could read the SOAP envelope into a
buffer and run their parser over it. As they parse they could figure out
what to do with each attachment and read it from the network stream. The
order must match. Is relaxing this requirement a huge simplification for
other scenarios?

2) This is a spec. bug. I'll get it fixed.

Thanks,

  =3D=3D Mike =3D=3D

This posting is provided "AS IS" with no warranties, and confers no
rights.