Robin wrote:
> I use the namespace of the body root element as a differentiator.
> I usually do this to support several major versions of a service
> interface by a single implementation.
>
> While I have never used REST, I don't think REST is polymorphic, REST
> is more than that, it is about a limited set of generic services.
The REST verbs are confined to a limited set for the HTTP case. The
behavior of GET and PUT are well defined for the desired intent and
documented specification. The exact work done is where the line of
polymorphism is drawn. POST, is wide open territory in that regard.
Because POST can do anything with the posted data, the noun (URI)
truely defines the work, not the verb (POST).
When people do odd things with GET and PUT, they are providing a less
polymorphic behavior and are perhaps creating an 'overload' definition
by the same name.
Polymorphism is possible with REST. It just isn't inforced with any
outwardly visible definition, without a form specification of the
VERBs behavior in relation to the NOUN (URI).
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
