On 10/18/07, Glen Daniels <[EMAIL PROTECTED]> wrote: > > > Hi folks: > > +1 from me *if* we make sure there's a flag to allow people to control > whether a given operation supports POX or not. Essentially I'm just > saying we should backport the SOAP-Response MEP to SOAP 1.1, and allow > the user to specify. By default the behavior should be as in Keith's > proposal, but if they indicate that a particular operation is using the > SOAP-Response MEP (this could also be a disablePOX flag or whatever),
How about using the disable REST flag for this without introducing another flag. it > should always return SOAP on a GET. > > Also... > > >> a SOAP 1.1 response uaing http content negotiation (A SOAP 1.1 > >> response will be went only when the request is SOAP 1.1 and there is > >> no matching value in the Accept header). > > If the request is SOAP 1.1, we should always return SOAP 1.1 regardless > of the Accept header, right? In this case the return will be the return will be SOAP 1.1 only is there was no matching ACCEPT header. Id a SOAP 1.1. request came with the header ACCEPT : text/xml then the response will be pox. Thanks, Keith. --Glen > > Sanjiva Weerawarana wrote: > > +1 from me. > > > > For some further discussion on this see [1]. In particular [2] gives > > rationale for why its ok to give more weight to POX over SOAP 1.1. > > > > Sanjiva. > > [1] > http://wso2.org/mailarchive/registry-dev/2007-October/thread.html#473 > > [2] http://wso2.org/mailarchive/registry-dev/2007-October/000540.html > > > > keith chapman wrote: > >> Hi Devs, > >> > >> There have been some thought on http content negotiation. With the > >> concept of builders and formatters we have now this could be > >> implemented trivially. The idea is to use the "Accept" http header to > >> serve the response requested by the client. While going through this > >> though I came across a issue though. This occurs when a request is > >> sent via a GET using a browser (Cause the browser automatically adds > >> the Accept http header). The Accept header sent by firefox is "Accept: > >> text/xml,application/xml,application/xhtml+xml,text/html;q=0.9 > ,text/plain;q=0.8,image/png,*/*;q=0.5". > >> The confusion comes in because text/xml is used for both SOAP and REST > >> responses. > >> > >> I believe having http content negotiation as a feature will be a nice > >> addition to Axis2. And I propose that we treat text/xml as a REST > >> response in implementing this. This would mean that you cannot ask for > >> a SOAP 1.1 response uaing http content negotiation (A SOAP 1.1 > >> response will be went only when the request is SOAP 1.1 and there is > >> no matching value in the Accept header). > >> > >> What do u think? Should we go ahead and implement this proposal? > >> > >> Thanks, > >> Keith. > >> > >> -- > >> Keith Chapman > >> WSO2 Inc. > >> Oxygen for Web Services Developers. > >> http://wso2.org/ > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
