Hi Rocky,

I liked the article and rambled on a bit about it here:

http://www.from9till2.com/

Could have done with your insights at the last MAAB meeting, when you done with Smart Client? ;-)

- David

Hey Rocky. Good article - with a couple of issues: http://www.theserverside.net/tss?service=direct/0/PostDiscussionReply/postReply&sp=l33434&sp=F&sp=l167170#167545

Cheers,
Ed

Hi Rocky,

I listened to you when you were speaking at .Net Rocks last month. There you mentioned that we need new languages/tools for SOA. At that time I didn't understand what did you mean when you were asking for new languages. This article really helped me understand your point view.

I also realized that at the company where I work, we already have a VB6 SO application that behaves like a router. We developed that application about 5 years ago. We receive emails that have XML in the body from different providers. The ‘router’ takes emails from the drop folder, extracts XML document and applies an XSLT for specific provider. After transformation is complete, the application parses XML and inserts data in to the database.

What I’m trying to say that we have tools to develop SOA software for awhile. However, you’re correct in senesce that many more can be done to help us to develop and support SOA applications.

Howdy

I like the ideas you have expressed in your articles. I have a feeling you are headed some where with all this. At any rate you sent me down a path of thinking.

It basically comes down to the fact that OOP should rule application development, RDBMS's are hidden in the corporate black hole and SOA bridges the gap.

Both you and David West confess that a relation DB isn't the ideal persistance mechanism but that they seem to be a necessary evil.

I wonder why you haven't talked about using a OODBM's for the application/object persistance, RDBMS for data distribution and SOA as the bridge between the two.

It is being discussed in the csla group with some liking the idea.

http://groups.msn.com/CSLANET/general.msnw?action=get_message&mview=0&ID_Message=18099&LastModified=4675519303041818456

I also have written some ideas at my blog http://www.freefallproductions.net/DasBlog/default.aspx

Rocky,

It would seem to me that a Covenant precludes a Contact. I would assume that when discovering a service, the Description is the Covenant. In essence this is a notification.

If the comsumer agrees to the terms set in the Covenant and is able to provide the entities set in the Covenant, the Contract would be established.