David

We support POST and GET but not PUT, DELETE. We have a JIRA about this
(adding fuller support for HTTP).
I think if we could lay out some patterns for mapping REST calls into
non-REST (or vice versa) then that would probably help us prioritize
adding PUT/DELETE support into the HTTP transport. For example, how
should we represent those as messages in Synapse?

Actually I think it would be pretty easy to do that by adding some
message context - we could even just add a simple property
(HTTPVerb?). Then a content-based filter (<switch>) could work off
each of the Verbs to do something useful.

Thoughts?

Paul

On Jan 10, 2008 5:15 PM, David Purcell <[EMAIL PROTECTED]> wrote:
> In looking through the synapse examples, there is mention of POX and a little 
> about REST, but I don't see true support for RESTful style services that take 
> advantage of all the HTTP verbs, for instance.  Is that pretty much the case, 
> or am I missing something?  I'm thinking of the following scenarios:
>
> 1.  We could expose a SOAP interface to the world, but the mediation would 
> translate to RESTful style if the end service is actually a RESTful service
>
> 2.  Synapse could simply perform some mediation but pass along a REST request 
> to a REST end service (maybe the message/payload doesn't need to be changed, 
> we just need to interrogate the request for security or auditing purposes).
>
> Thoughts?
>
> Thanks,
>
> David
>
> ===============================
> David Purcell
> Systems Architect
> MN State Colleges and Universities
> [EMAIL PROTECTED]
> ==============================+
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to