From Sam Ruby's comments pages, on SOAP, WS-xxx, and CORBA...
Sam writes: What I like about the WS stack is that if all you need is SOAP document literal, all you need to implement is extremely small.
Reply: Yes, a great boon for adoption.
Dave Winer writes: SOAP was created by people who develop applications, so it didn't suffer from a lack of applications to pull it through.
Reply: Yes, a great boon for adoption! 8^) You folks were not about to create a CORBA first and then build apps later.
And this is a problem, as far as I can see, with the WS-xxx stuff taking place today, which is more like CORBA than it is like XML-RPC. Shouldn't the WS-xxx folks be working with OMG on that stuff? Why isn't "Enterprise Web Services" simply the next CORBA 4.0 release with SOAP optionally (but efficiently) slipped into the stack? There are high performance, open source implementations of much of CORBA 3.0.
I can think of at least one reason why not, but it's not a good reason.
No comments:
Post a Comment