The Artima Developer Community
Sponsored Link

.NET Buzz Forum
Marathon

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Dave Bettin

Posts: 94
Nickname: dbettin
Registered: May, 2004

Dave Bettin is a .Net Service Developer
Marathon Posted: Mar 30, 2005 8:52 PM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Dave Bettin.
Original Post: Marathon
Feed Title: Dave Bettin on Services
Feed URL: http://www.davebettin.com/me/rss.aspx
Feed Description: Bettin' on .Net Service Development
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Dave Bettin
Latest Posts From Dave Bettin on Services

Advertisement

I had a couple of comments in response to my entry about Indigo's peer-to-peer support. The response has manifested into two separate issues. 

The first issue is centered on the fact that the duplex contract example that I pointed at is not truly peer-to-peer. And, I would have to agree that the example is not a true peer-to-peer pattern. However, the intended purpose of the link was to direct individuals to a great example of a powerful Indigo feature that can enable peer-to-peer communication. Although, the example was not peer-to-peer it does provide some insight into how the duplex contracts work.

 

The second issue focuses on the semantic mismatch between Indigo’s object oriented service view and the pristine service oriented perspective. After, attending events such as PDC’03, Indigo Day, and the SDR, I have witnessed Indigo mature from a quantitative product to a qualitative product.  IMO, initially Indigo focused on features, features, and more features and Microsoft now has realized it is more important to release a product that is of high quality and very usable for the “average joe” object oriented developer then focus on the features. Unfortunately, this means a lot of cool and interesting features have been dropped from Indigo V1. But as a result of this context switch we will get a very clean programming model that abstracts away the underlying WS-* goop, yet still allows plumbers to play around with the pipes. And, I also believe Indigo’s object oriented model is now prepared for the inevitable inception of service oriented development languages. I can envision a service programming language or maybe even a domain specific language mapping cleanly to the Indigo programming model. Although, today you have to program Indigo in your CLR language of choice; I believe tomorrow it will be a completely different story.

 

Indigo is a marathon and the race is only beginning.

Read: Marathon

Topic: Expanded internal interest in Scrum Previous Topic   Next Topic Topic: CodeZone? Another marketing driven community doomed to fail.

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use