[Mono-list] .Net App Server
Thu, 18 Jul 2002 10:53:13 -0700 (PDT)
--- Tom Reilly <firstname.lastname@example.org> wrote:
> 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
> .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.
I prefer to use the new classes and interfaces
specifically created for supporting EJB like
functionality than using bare bones APIs, whatever
that platform could be. Now, in that case, you can
equally use Java.
> EJB's have lots of problems too, many argue they are
> too complex
> and try to solve too many problems with one
A good solution can isolate you from the original
complexity of problem, bu othe solutions sometimes at
some point in time they parallel the problem, and a
server side app it's complex thing. Look around, you
have naming, pooling, persistence, scalability, fault
tolerance, etc. All that is build for you by the EJB
> ridiculous how much money is spent on full blown
> J2EE app servers
> that only run apps using JSP, servlets and JDBC.
This is how the people are using an app server not a
app server problem by itself. I agree that it's
ridiculous to use an expensive app server like that.
If that where the case you can use the great open
source projects of Apache's Jakarta: Tomcat, Turbine,
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes