> If that's true, then they're wrong. HTTP defines a very useful API.
> They can argue that for their particular application, that those APIs
> are insufficient. But they can't argue that HTTP doesn't give them
> any application semantics to work with, because that's all it
> does; it's
> an *APPLICATION* protocol ferchristsakes.
I would carefully claim that both SOAP and HTTP are protocols - they
don't define any APIs.
A new year - an old discussion :)
This archive was generated by hypermail 2b29 : Fri Apr 27 2001 - 23:17:47 PDT