[acs-wg] Data transport with SOAP.

[Michael Behrens]

Thanks for the quick answers - comments below.

Keisuke Fukui wrote:

> Hi Mike,
>
> Thanks for your reviewing and comments!
>
> Michael Behrens wrote:
>
>> SOAP comments - looks good.
>> I wonder if a distinction is necessary between having 1..n 
>> attachments or just 1 attachment.
>
>
> Although it is not explicitly mentioned, the specification sounds like
> that the URI as a reference in the SOAP message can point either 
> attachment
> in the multipart MIME or *external storage*. i.e. The URI could point 
> either
> of them without specifying which of them. If it is the case, I guess
> we can get two for one by this; we can leave the decision up to the
> clients and processed by the implementation of the ACS repository with
> single rendering of the ACS Request message such as "Create".
> If it is ever possible, counting may introduce the complexity.
> Do you have specific demands to have counting of the MIME multi parts?

I do not believe I have requirements regarding this.

>
>> Also, where is the AA Description information? (parameter to create 
>> porttype or as an attachment)
>
>
> I intended in the diagrams as:
> In the case of discrete type, it should be the first part in the 
> multipart
> MIME, besides the SOAP message. In the case of a bundled file, it is 
> inside
> the bundle.
>
>
> BTW, I'm concerned with alternative specs that I listed as "other
> specifications". Does anyone have knowledge of latest status for these?

I do not.

>
>>
>> P.S. I have not had time to review the draft with regard to 
>> terminology and I know the deadline is today (tomorrow our time).
>
>
> Thanks. I will wait for your posting.
>
>  -Keisuke
>
>
Okay, expect it in about 22 or 23 hours. :)

-- 
Michael Behrens
R2AD, LLC
(571) 594-3008 (cell) *new*
(703) 714-0442 (land)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/acs-wg/attachments/20050825/3c2e9b0c/attachment.htm