Re: Mapping WSDL meps to the HTTP binding

According section 6.4.1 of the current draft, the HTTP binding supports 
in-out and (robust) in-only.
It also says that the HTTP binding may supports other meps like the 
outbound ones.
I do not recall when the decision was made however...
    Youenn

Sanjiva Weerawarana wrote:
> youenn fablet wrote:
>>
>> Reading the HTTP binding specification I have the following comment.
>> Currently the mapping from WSDL meps to HTTP binding  messages is 
>> described in section 6.4.1.
>> Basically it says that the wsdl input message is the http request 
>> message and the wsdl output message, if any is the http response 
>> message.
>> I wonder whether this description is sufficient for the inonly and 
>> especially robust-inonly wsdl meps.
>> At least, we might need to specify the HTTP code to use in the 
>> response, especially for the robust-inonly.
>> Should it be 200, 202 or left unspecified as it is currently?
>> Are there other things that need to be specified?
>> What do you think?
>
> The HTTP binding does not support these MEPs. I thought I wrote that 
> down somewhere ..
>
> If we want to support them we must specify the details as you noted. 
> And indicate that other MEPs (e.g., outbound ones) are not supported.
>
> Sanjiva.

Received on Thursday, 16 November 2006 21:52:12 UTC