Re: [AXIS2] Proposal to implement http content negotiation - keith chapman - org.apache.ws.axis-dev

10 messages in org.apache.ws.axis-devRe: [AXIS2] Proposal to implement htt...

From	Sent On	Attachments
keith chapman	Oct 16, 2007 10:17 pm
Paul Fremantle	Oct 17, 2007 12:05 am
Sanjiva Weerawarana	Oct 17, 2007 8:13 pm
Glen Daniels	Oct 18, 2007 3:41 am
keith chapman	Oct 18, 2007 5:37 am
Nicholas L Gallardo	Oct 18, 2007 2:14 pm	.gif, .gif, .gif
keith chapman	Oct 18, 2007 6:53 pm	.gif, .gif
Sanjiva Weerawarana	Oct 19, 2007 5:27 am
keith chapman	Oct 21, 2007 12:51 am
keith chapman	Nov 20, 2007 10:24 pm

	Permalink for this message Paste this link in email or IM:
	Permalink for this thread Paste this link in email or IM:
	Atom feed for this thread Paste this URL into your reader:

Subject:	Re: [AXIS2] Proposal to implement http content negotiation	Actions...
From:	keith chapman (keit...@gmail.com)
Date:	Oct 18, 2007 5:37:10 am
List:	org.apache.ws.axis-dev

On 10/18/07, Glen Daniels <gl...@thoughtcraft.com> 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.

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?

	Start a set with this search
	Include this search in one of my sets
	Exclude this search from one of my sets
	Permalink to these results Paste this link in email or IM:
	Atom feed for tracking future search results Paste this URL into your reader: