On 12/17/07, Subbu Allamaraju <subbu.allamaraju@...> wrote:
> which only proves that doing good REST is as easy as bad REST. The
> trouble is that the "action-oriented" mindset maps very well into SOAP
> and not REST.

And the resource mindset maps poorly to SOAP :-)

> This brings up another question. Why do people want to provide both
> SOAP and REST interfaces?

Because for any given service it's quite likely to find consumes who
will appreciate one and not the other, and adding a checklist is
easier than taking a stand.

> When they decide to do, do they want to use
> the same code base to process the requests? I can see lots of issues.
> Has anyone on this list got experience doing both for the same
> application?

From personal experience offering both SOAP and SOAP-w/o-envelope as
interchangeable protocol bindings is fairly trivial with most modern
WS-* stacks.

But building around the REST architecture and then trying to map it to
SOAP, you end up losing features on the SOAP interface or
over-complicating it. And the reverse is true if you start out from
the WS-* architecture and try mapping it to REST [1].

Assaf

[1] http://blog.labnotes.org/2007/12/17/web-architectures-and-http-mediocrity/

>
> Subbu
>
> On Dec 17, 2007, at 10:15 AM, Assaf Arkin wrote:
>
> > On 12/17/07, Subbu Allamaraju <subbu.allamaraju@...> wrote:
> >> That was quick :)
> >
> > It was surprisingly easy, couple of hours.
> >
> > Assaf
> >
> >>
> >> Great.
> >>
> >> Subbu
> >>
> >> On Dec 17, 2007, at 1:59 AM, Assaf Arkin wrote:
> >>
> >>> On 12/16/07, Subbu Allamaraju <subbu.allamaraju@...> wrote:
> >>>> +1
> >>>>
> >>>> I just tried to "refactor" this API
(http://www.subbu.org/weblogs/main/2007/12/a_restful_versi.html
> >>>> ) to be resource oriented, and it is not that hard.
> >>>
> >>> Subbu, here's a slightly different take on the same principle:
> >>> http://blog.labnotes.org/2007/12/17/dehorrible-restifying-simpledb/
> >>>
> >>> Assaf
> >>>
> >>>>
> >>>> Subbu
> >>>>
> >>>> On Dec 16, 2007, at 12:57 PM, Steve Loughran wrote:
> >>>>
> >>>>> On Dec 16, 2007 5:49 PM, Julian Reschke <julian.reschke@...>
> >>>>> wrote:
> >>>>>> Subbu Allamaraju wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>> This is a variant of what I call as SOAPy REST (http://subbu.
> >>>>>>> org/weblogs/ main/2007/ 10/soapy_ rest.html
> >>>>>>> <http://subbu.org/weblogs/main/2007/10/soapy_rest.html>
> >>>>>>> ). Whoever wrote this API had no idea of why they were
> >>>>>>> providing a
> >>>>>>> resource centric interface. Yet another HTTP API!
> >>>>>>
> >>>>>> No, it's even much Much MUCH worse -- it uses GET for non-
> >>>>>> retrieval
> >>>>>> actions.
> >>>>>
> >>>>> I nominate it for the 2007 Restless awards, in the much contested
> >>>>> category of
> >>>>>
> >>>>> "things that claim to be RESTful but do side effects in their
> >>>>> GETs"
> >>>>> along with the ever popular
> >>>>> "SOAP endpoint in disguise" category
> >>>>>
> >>>>> I know this mailing list has not, historically, had such awards,
> >>>>> but
> >>>>> now is as good a time to start as any....
> >>>>>
> >>>>>
> >>>>>
> >>>>> Yahoo! Groups Links
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Yahoo! Groups Links
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
>
>