[Mono-list] Why mono has a long way to go..
Tue, 04 Nov 2003 22:07:22 +0100
On dt, 2003-11-04 at 21:46, Kenneth Benson wrote:
> Lluis, can you tell me where to find some info on Indigo?
Here you'll find more info:
> -----Original Message-----
> From: Lluis Sanchez [mailto:firstname.lastname@example.org]
> Sent: Tuesday, November 04, 2003 11:06 AM
> To: Johan du Plessis
> Cc: email@example.com
> Subject: Re: [Mono-list] Why mono has a long way to go..
> > Hello everybody.
> > I love mono. Open-source dotnet. But for my line of work it is
> > and will remain so for a long time. You see certain parts seems to
> > ignored in mono and it is of great concern to me (and I hope
> No parts of .NET are ignored, it is just that nobody has started
> contributing those parts, and the core Mono team has other priorities.
> > 1) Code Access Security
> > Little has been done in this area. And I believe in the great
> > motto : You can't hack in security afterwards, it will lead to a
> > CAS spans most of the class libraries.
> See "Unscheduled activities" section on the mono roadmap for info
> > 2) Messaging
> > .NET is to compete with J2EE. .NET has messaging based on MSMQ. We
> > no implementation of this, and no credible alternative. Without it
> > can't be taken seriously in the enterprise domain.
> > 3) EnterpriseServices
> > We have no transaction support. I do believe that COM+ will be a
> > bit difficult to duplicate. The closest we can get to this is using
> > CORBA... And open-source CORBA itself has neglected Transactions. It
> > doesn't seem if either mySQL or postgreSQL supports the XA
> > standards. Yet again, for any serious EE application this is
> All we want Mono to be a credible platform for building enterprise
> applications, and I'm sure that Mono's support in this area will grow
> once the runtime, core and basic libraries become more complete and
> The landscape has changed quite a lote since the last PDC. The
> will be to build Indigo, because it replaces Messaging and
> However, if there is people really interested in EnterpriseServices
> Messaging, I think that the right path is to build them on top of
> Indigo, since it provides most of the needed infrastructure (it
> a transaction manager, reliable messaging and so on).
> > Now most of the people will most likely say, shut up and pitch in
> > these components span multiple parts of the .NET implementation as
> > as other open-source projects.
> > If anybody has any ideas on how we are going to solve this problem
> > me an e-mail please. If nothing else I do hope that people starts to
> > talk about these components.
> > Cheers
> > Johan du Plessis
> > _______________________________________________
> > Mono-list maillist - Monofirstname.lastname@example.org
> > http://lists.ximian.com/mailman/listinfo/mono-list
> Mono-list maillist - Monoemail@example.com