[Mono-list] .Net App Server
Thu, 18 Jul 2002 13:18:42 -0400
I'd say .Net has all the functionality of EJB minus
automatic RDBMS object persistance. You can use
attributes to get method level transactions and security.
.Net remoting makes exposing objects remotely a breeze (and
you get to chose between a nice fast binary protocol or SOAP).
And you get it all for free.
EJB's have lots of problems too, many argue they are too complex
and try to solve too many problems with one technology. Its
ridiculous how much money is spent on full blown J2EE app servers
that only run apps using JSP, servlets and JDBC.
> -----Original Message-----
> From: Rogelio Robles [mailto:email@example.com]
> Sent: Thursday, July 18, 2002 12:44 PM
> To: Tom Reilly; 'Miguel de Icaza'; Dave Bettin
> Cc: firstname.lastname@example.org
> Subject: RE: [Mono-list] .Net App Server
> > An application server usually comprises:
> > 1) HTTP(S) server
> > 2) RDBMS connectivity (ADO.NET)
> > 3) Dynamic web page scripting language (ASP.NET)
> > 4) clustering support (load balancing/fail over)
> > 5) Web Services (.NET remoting)
> > 6) application packaging/deployment functionality
> > 7) administration/monitoring tools
> > So take Apache, Mono and implement 4,6,7 and you'd
> > have
> > a Mono app server.
> To build an application server you are missing a very
> important piece which is a similar concept to Java's
> J2EE spec and API: an Enterprise Java Beans (EJB)
> NET framework has all the building blocks for that,
> but they didn't build it. Maybe it was too much.
> My guess is that Microsoft will come with that in
> future .NET releases, in this specific area they don't
> even compare, like apples and oranges. This will
> require some iterations to get it correctly.
> Do You Yahoo!?
> Yahoo! Autos - Get free new car price quotes