The Artima Developer Community
Sponsored Link

.NET Buzz Forum
A Mono developer's thoughts about Indigo

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
Christian Weyer

Posts: 616
Nickname: cweyer
Registered: Sep, 2003

Christian Weyer is an independent Microsoft MSDN Regional Director and expert for Web services.
A Mono developer's thoughts about Indigo Posted: Nov 6, 2003 4:18 AM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Christian Weyer.
Original Post: A Mono developer's thoughts about Indigo
Feed Title: Christian Weyer: Web Services & .NET
Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/cweyer/Rss.aspx
Feed Description: Philosophizing about and criticizing the brave new world ...
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Christian Weyer
Latest Posts From Christian Weyer: Web Services & .NET

Advertisement

Lluis from the Mono team speaks Indigo. And obviously he got the 'message' of Indigo - and this is good to see:

The first thing to say about Indigo is that it does not contain revolutionary technology. It just takes the best of ASMX, WSE, Remoting, Messaging and Enterprise Services to create a new framework for building enterprise applications based on a Service Oriented Architecture model.
However, the great value of Indigo is that it integrates in a coherent way all those diverse technologies, by providing a common communication stack, common security features, transaction management and extension mechanisms.

At the end of his article he mentions Mono's roadmap regarding all the Indigo-related technologies - which should be a cue for all of us:

Generally speaking, the strategy will be to finish those technologies for which there is work in progress, while starting the work on the new Indigo framework. Here is some more detail:

  • Remoting: It will still be very useful in some scenarios. Missing features will be completed and bug fixing will continue.
  • Web Services (ASMX): It is currently used in many applications, and it is mostly feature complete, so it makes sense to fix the remaining bugs and release it as part of Mono 1.0.
  • Enteprise Services: Right now, the development of System.EnterpriseServices is not a priority, since nothing is implemented in this namespace and it will be replaced by the new service model. However, if there is interest in implementing support for it, the best approach would be to implement it on top of Indigo (that is, using the transaction management and hosting features that Indigo provides).
  • System.Messaging: No plans for this. Indigo's messaging architecture is very different from that of MSMQ.
  • WSE: Although its dead is already scheduled, it makes sense to continue its development since the technology that it provides will be reused in the development of Indigo, and it will be a good Indigo replacement until it is released.

 

Read: A Mono developer's thoughts about Indigo

Topic: Quiet CPU Fans? Previous Topic   Next Topic Topic: .NET Nightly 43

Sponsored Links



Google
  Web Artima.com   

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