OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ws-rx] i006 -- a proposal


Anish Karmarkar wrote:

> I would like to convert my suggestion in my previous email (can't 
> provide a reference as I can't find the email in our archive) to a 
> proposal to resolve i006:
>
> Use the wsrmp:DeliveryAssurance element (as defined in the resolution 
> of i009) in the CS message as follows:
>
> <wsrm:CreateSequence ...>
>   <wsrm:AcksTo ...> wsa:EndpointReferenceType </wsrm:AcksTo>
>   <wsrm:Expires ...> xs:duration </wsrm:Expires> ?
>   <wsrm:Offer ...>
>     <wsrm:Identifier ...> xs:anyURI </wsrm:Identifier>
>     <wsrm:Expires ...> xs:duration </wsrm:Expires> ?
>     ...
>   </wsrm:Offer> ?
> *  <wsrmp:DeliveryAssurrance .../>?*
>   ...
> </wsrm:CreateSequence>
>
> This would allow the Application Sender to signal the RMD/AD of the 
> DA. If the DA is something that is not supported or conflict the 
> policy at the RMD/AD, the RMD may send a CreateSequenceRefused fault. 
> This element of course does not change the protocol on the wire, but 
> lets the RMD/AD know exactly the DA that is expected for the Sequence.

Perhaps the fault could include detail info on which DAs are supported 
by the RMD/AD.

Tom

>
> -Anish
> --
>


-- 
----------------------------------------------------
Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]