[Mono-list] Why mono has a long way to go..

[Lluis Sanchez]

Hi

> Hello everybody.
> 
> I love mono. Open-source dotnet. But for my line of work it is unusable
> and will remain so for a long time. You see certain parts seems to be
> ignored in mono and it is of great concern to me (and I hope others).

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 security
> motto : You can't hack in security afterwards, it will lead to a mess.
> CAS spans most of the class libraries.

See "Unscheduled activities" section on the mono roadmap for info about
this.

>  
> 2) Messaging
> 
> .NET is to compete with J2EE. .NET has messaging based on MSMQ. We have
> no implementation of this, and no credible alternative. Without it we
> can't be taken seriously in the enterprise domain.
> 
> 3) EnterpriseServices
> 
> We have no transaction support. I do believe that COM+ will be a little
> 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 Transaction
> standards. Yet again, for any serious EE application this is mandatory.

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
stable.

The landscape has changed quite a lote since the last PDC. The priority
will be to build Indigo, because it replaces Messaging and
EnterpriseServices. 

However, if there is people really interested in EnterpriseServices and
Messaging, I think that the right path is to build them on top of
Indigo, since it provides most of the needed infrastructure (it provides
a transaction manager, reliable messaging and so on).

Lluis.

> 
> 
> Now most of the people will most likely say, shut up and pitch in but
> these components span multiple parts of the .NET implementation as well
> as other open-source projects. 
> 
> If anybody has any ideas on how we are going to solve this problem drop
> 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  -  Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list