Good, Fast, Cheap Pick TWO :)
On Sat, Mar 29, 2008 at 8:59 AM, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: > On Fri, Mar 28, 2008 at 1:24 PM, Rob Eamon <[EMAIL > PROTECTED]<reamon%40cableone.net>> > wrote: > > > > Interesting thought--wouldn't a fine-grained interface tend to pull > > against the goals of service orientation? Doesn't this increase > > coupling? Does it tend to required stateful interactions--e.g. > > invoke "method X" before invoking "method Y"? Aren't these a couple of > > the issues encountered with OO approaches of years past that were found > > to be inflexible? > > > > -Rob > > REST requires stateless interactions. A RESTful service exposes a set > of resources. A resource is some "thing" that you want to interact > with -- it could be something very fine-grained, such as the current > luminosity setting of a single lightbulb, or something very coarse, > such as all lights in a building, or something derived or calculated, > such as the level of energy consumed by the building during a specific > time period. > > A RESTful service uses hypermedia as the engine of application state. > i.e., a resource uses hyperlinks to refer to related resources. Bear > in mind that in REST you don't have "method X" and "method Y", but you > may have to GET "resource X" before you can POST to "resource Y" > because "resource X" provides the means for you to get the URL of > "resource Y". Note, though, that if you can obtain the URL of > "resource Y" without doing a GET of "resource X", you don't have to > GET "resource X". > > Anne > > > > > --- In > > [email protected]<service-orientated-architecture%40yahoogroups.com>, > "Anne Thomas > > Manes" <[EMAIL PROTECTED]> wrote: > > > > > > > > > (Note that the RESTful service can still be coarse-grained -- but the > > > interface [the resources it exposes] is fine-grained.) > > > > > > Anne > > > > > > -- ------------------------------------------------------------------------- This message contains confidential information and is intended only for the intended recipient(s). If you are not the named recipient you should not read, distribute or copy this e-mail. Please notify the sender immediately via e-mail if you have received this e-mail by mistake; then, delete this e-mail from your system.
