On 10/07/06, Mark Baker <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
>
>
> On 7/10/06, Steve Jones <[EMAIL PROTECTED]> wrote:
> > > That's difficult to quantify, of course. It depends a lot on the data
> > > itself. As a low watermark though, we know;
> > >
> > > work(Web services) = work( solving interface problem) + work ( solving
> > > data problem )
> > > work(Web) = work( solving data problem )
> >
> > Do we? I certainly don't. You still have to define the operational
> > interface, even though it is a document post rather than a defined
> > interface document. If you don't define the operations available to
> > consumers then THEY WON'T KNOW ABOUT THEM.
>
>
> Steve - it is *axiomatic* in REST that all services expose the same
> "operational interface", so yes, we do know that.
>
> http://roy.gbiv.com/pubs/dissertation/rest_arch_style.htm#sec_5_1_5
>
Nope, that is the INVOCATION mechanism (the execution context to use
the SOA RM term), that isn't the operational interface that consumers
use.
With our lightbulb we have
1) The URI
2) The data format of the request/response
3) The meaning of that request/response
"PUT" is not an operational interface for a service consumer, it is
the execution context that enables the consumer to be connected with
the producer.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> 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/
