On Jul 11, 2006, at 8:15 PM, Dan Creswell wrote:
> Jan Algermissen wrote:
> > On Jul 11, 2006, at 5:54 PM, Dan Creswell wrote:
> >
> >> And as it appears that's what you'd have to do many people are
> >> wondering
> >> how that's much better than defining it all on some contract/
> interface
> >> be it implemented via RPC or some other mechanism.
> >
> > Because there will be integration at some point and with e.g. RPC
> you
> > have to deal with:
> >
> > - the behavioural contract
> > - the API
> > - the data
> >
> > with REST you only need to consider
> >
> > - the data
> >
> > IMHO it is much easier to *only* having to translate between
> > different data representations of state than it is to translate
> > between different behavioural and API contracts *and* the data.
> >
>
> How do you know what to translate and to what?
That's the integration work to be done. HTTP does not take that away,
it just simplifies it.
>
> And how do you know what's going to be done with what you translate -
> i.e. what behaviour is behind that get or put or whatever?
From the HTTP specs, where PUT etc. is defined.
Maybe what you are missing is that there is also link traversal
involved. The semantics of the links (which I know because I know the
mime type) are enabeling that I make choices. These choices are maybe
what's missing from the overall picture?
>
> Think I'm just dumb........
>
The best way really to achieve REST epiphany is to try it out for
yourself on a little distributed systems example and take your
questions to rest-discuss.
Jan
> > Jan
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>
>
>
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/
