[Mono-list] .Net App Server
Thu, 18 Jul 2002 17:53:53 -0700 (PDT)
I agree. Hopefully, the mono community will continue
to grow to support the availability of such services.
A "Mono" App Server is definitely needed, to have a
full fledged cross platform environment.
--- Lluis Sanchez <email@example.com> wrote:
> MS has COM+ as App Server, and the
> System.EnterpriseServices namespace is
> just a binding to COM+. So to implement
> EnterpriseServices we need to
> "emulate" COM+ architecture and all the services it
> In fact, a "Mono" App Server would not need to use
> System.EnterpriseServices or COM+ architecture, it
> could be something new.
> However, why not? It's already defined, it is not
> bad, and without the
> limitations of COM it would be even better.
> Mono will be very useful for building client
> applications and for light
> webs, but without an Application Server it will be
> useless for building real
> enterprise applications (distributed applications,
> with high scalability and
> availability requirements). Something has to be
> done. My wish list for a
> .NET application server would be:
> a.. Support for standard component services:
> transactions, object pooling,
> db connection pooling, just-in-time activation, etc.
> b.. Support for Message Queuing.
> c.. Eeeeeasy to manage, with a nice and colorful
> management console.
> d.. Support for clustering / load balancing
> e.. Fast and powerful component deployment system,
> with support for hot
> deployment, distributed deployment and good
> component version management.
> f.. Portable, of course.
> A lot of work to do indeed, although I would enjoy
> working in such a
> ----- Original Message -----
> From: "Miguel de Icaza" <firstname.lastname@example.org>
> To: "Rogelio Robles" <email@example.com>
> Cc: "Tom Reilly" <firstname.lastname@example.org>; "Dave
> <email@example.com>; <firstname.lastname@example.org>
> Sent: Thursday, July 18, 2002 8:54 PM
> Subject: RE: [Mono-list] .Net App Server
> > >
> > > To build an application server you are missing a
> > > important piece which is a similar concept to
> > > J2EE spec and API: an Enterprise Java Beans
> > > container.
> > >
> > > NET framework has all the building blocks for
> > > but they didn't build it. Maybe it was too much.
> > System.EnterpriseServices namespace:
> > Miguel
> > _______________________________________________
> > Mono-list maillist - Monoemail@example.com
> > http://lists.ximian.com/mailman/listinfo/mono-list
> Mono-list maillist - Monofirstname.lastname@example.org
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes