Let's take REST out of the equation for a second.
Do you consider the standard relational database as having a
polymorphic interface?
do('Select * from Employees')
Is 'do' polymorphic?
Is 'select' polymorphic?
Why/Why Not?
Thanks,
Jeff
--- In [email protected], "Nick Gall"
<[EMAIL PROTECTED]> wrote:
>
> "Using this definition, you could say that the combination of REST
services
> are polymorphic. You can not, however, say that an *individual*
service is
> polymorphic"
>
> Why in the world not? Different URIs can have the "same verb
applied to
> them", e.g., GET. So GET is polymorphic. What's so hard to grasp
about this?
>
> If basic OO concepts are this widely misunderstood, no wonder REST
is so
> widely misunderstood.
>
> "If the interface is explicit, then the polymorphic context should
be
> implied in the message." Actually it's dispatched off he URI.
> http://rest.nick.com/employee/123 dispatches to my employee
processing code
> and http://rest.nick.com/product/123 dispatches to my product
processing
> code. URI dispatching is done billions of times every day with
great ease
> and good enough efficiency. So what's the problem with polymorphic
REST
> verbs.
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/
