> >
> >Given WSDL does not provide behavioral contracts (just functional ones
> >over data)
> >how can we:
> > i) describe the behavior?
> > ii) monitor services against their described behavior?
> > iii) guarantee that services do behave correctly?
> >All of course in a standard and unambiguous way. If we can do this then
> >we can
> >ensure that different implementations over different transports do the
> >right thing
> >at right time and that way ensure interoperability and substituability
> >of participant
> >services.
>
> Since REST eliminates the design-time behavioural aspects and instead uses
> runtime discovery of possible state transitions+shared understanding of the link
> semantics the above suggests that REST is a promising candidate - at least more
> promising than architectural styles that make behavioural semantics part of the
> contract, eh?
So your REST application already can account for and react correctly to every
possible piece of content that the entire internet contains, and make it
possible for you to use it directly? You can only behave based on what you
know, and that includes the behaviors that are available. Mime-types control
how you handle known types of data which are well formatted. Nothing, but
explicit application programming controls the application behavior when the type
is not known, or the format is abnormal.
We've seen plenty of viruses/worms/bugs revealed by web browsers and email
clients which haven't had appropriate behaviors at their disposal. There's no
silver bullet down the REST path in that regard...
Gregg Wonderly
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
