Re: Dynamic invocation vs. late/dynamic binding

Hi Mark,

> > I guess we're back to the REST vs. WS debate; your program cannot
> > manipulate those shapes in a meaningful way without an understanding
> > of what an oval is vs. a square.
> 
> Of course you can!  All you need in order to create an abstraction
> is commonality.  Can't you "meaningfully" treat brown cows and black
> cows as cows?
> 
> Where's the disconnect here?  Surely you've used polymorphism before?

Of course, but as you said below I didn't think you were just looking
for polymorphism. So it has nothing to do about being colorblind 
about cows.

> (which, in case you were wondering, the Shape example isn't trying to
> demonstrate .. exactly)

I'm afraid you've lost me somewhere. I don't see how a *non-human*
(or should I say inhuman? ;-)) REST automaton can just do a GET 
on an opaque URL and magically understand the data while an automaton
driving a non-REST POST with the URL contained inside the SOAP
envelope cannot. 

It seems to me that we're back to the "REST can, but others can't"
position which I cannot accept.

Sanjiva.