I applaud you, G, for the words about HTTP. I would add SOAP to this camp. I compare HTTP to Assembler, SOAP â to C and WSLD â to C++/Java.
As of CORBA, there were two major causes for the failure and I do not know which one was more significant:
1) CORBA ties participating parties together and requires significant expertise as for development as for maintenance;
2) CORBA, when it appeared (was not open-source, actually), got between two fighting camps â MS and all others. It allowed to integrate apps from both camps but camps were not ready for a dialog (yet).
Plus, CORBA has not failed, itâs got âunder the deskâ: it exists in the all vendor implementation of J2EE and most of databases; application developers simply do not know about it.
Cheers,
- Michael PoulinGautham Kasinath <[EMAIL PROTECTED]> wrote:
Hey there,
Well, I was confused by the line: "Well, it tells us that HTTP is a
higher level "thing" than RMI, IIOP,"
How do you define the "thing"?
IMHO, HTTP is only a transport. Hence in the grand design of Service
Oriented Architecture (of which Web Services may be a means), HTTP
plays a very insignificant role.
CORBA however, was a separate paradigm in computing, IMHO. I guess it
was mostly the open sources answer to D-COM. However, I am unclear
about the causes of its failure. I Will need to explore that avenue.
Cheers
G
--- In service-orientated-architecture@ , "Mark Baker"yahoogroups. com
<[EMAIL PROTECTED]> wrote:
>
> On 6/28/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> > Mark Baker wrote:
> > > On 6/28/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> > >
> > >>Humm, but it has been said here that HTTP is an application
layer protocol. The
> > >>semantics of INVOKE are well defined. A remote reference is
indicated in the
> > >>payload which is the service as a URI is in HTTP. The
parameters of the method
> > >>call are arbitrary, but particular to the service, just like the
payload of POST
> > >>or PUT. The INVOKE always returns a reply as HTTP does. Help
me understand
> > >>what is not uniform about that?
> > >
> > > You have to INVOKE an operation. That operation is the application
> > > layer semantic.
> >
> > Right, and with HTTP, the message layer semantics that transpire
based on you
> > invoking a HTTP operation are at the same level as the eventual method
> > invocation on the remote end of an RMI INVOKE operation.
>
> That seems right, though it's possible that we might disagree about
> the meaning of "message layer semantics" and "eventual method
> invocation".
>
> In both cases, remote, application layer operations are being invoked
> over a network.
>
> > There are no real
> > differentiating factors other than nomenclature here are there?
>
> Well, it tells us that HTTP is a higher level "thing" than RMI, IIOP,
> or how SOAP is commonly used, because it provides the operations being
> invoked while the others do not. Considering how the entire Web
> services architecture is premised on it being a lower level thing, I
> think that's significant.
>
> Mark.
>
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less. __._,_.___
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.
