Re: [service-orientated-architecture] Re: SOA Reference Architecture

[Steve Jones]

I do wish GMail would do > indents....

On 29/06/06, Mark Baker <[EMAIL PROTECTED]> wrote:

On 6/28/06, Steve Jones <[EMAIL PROTECTED]> wrote:
> I want to be able to define my interface, to share that with others and have them consume that interface (in a tool) and then communicate.

Well then, you've got a problem right there. With a REST based
approach, the interface is defined for you. Your job is to identify
the resources and define the data formats. Everything else is just
the exchange of that data between those resources.

 

[SJ] An interface defines the FUNCTION as well as the data.  Data exchange is only one small part of a service definition.  Some functions never exchange any data for instance.  I might be very thick, but when I define a service interface I think in terms of the capabilities that it provides, these don't often get reduced to just resources and data.

> WSDL is VERY simple when you have the right tools, REST might have advantages over it, but does it really progress the state of the art at all?

Absolutely. I used to develop CORBA apps, now I use the Web to
develop similar apps. Without a doubt, it's been an improvement. A
dramatic one, in fact. Far simpler, more reliable, far more resilient
to change (due to the improvement in loose coupling), etc..

 

[SJ] But is REST that much better than WSDL?  I'm not seeing it

> We are arguing over two different forms of ASCII RPC here (eventing aside).

No, we aren't. See;

http://www.ics.uci.edu/~fielding/pubs/dissertation/evaluation.htm#sec_6_5_2

 

[SJ] I'd disagree with those two paragraphs as as a consumer or a producer the real world effect is the same and while there are some different elements I'm not seeing how it isn't just a remote procedure call.  You can do indirection and mediation using IIOP if you want to do (hell I've done it).  We appear to be arguing on semantic differences and points of elegance rather than just getting on an addressing the harder problems.  Stuff happens at point A, point A calls point B (potentially passing stuff), something happens, potentially B sends stuff back to A.  I might be missing something but that describes REST/SOAP/IIOP/RMI/rsh/etc and in my simple world is what RPC is all about.

 

Mark.

__._,_.___

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.

---

__,_._,___