On Wed, 5 May 1999 [EMAIL PROTECTED] wrote:
> On Wed, 5 May 1999, Ted Neward wrote:
>
> > How about this: instead of running a web server, run a generic application
> > server (EJB, CORBA, who cares) that has a "servlet" (sorry to reuse the
> > term) that listens on port 80, understands HTTP, and hands back HTML
>
> Why bother? Most application servers I've seen allow for using a web
> server as part of their architecture. Their other feature is taht of
> requiring deep pockets. :)
>
> > resources? Six of one, half-dozen of the other, you might argue, but most
> > application servers are starting to go the
> > clustered/load-balancing/fault-tolerance route, and if your application
> > server is an EJB server, your HTTP SessionBean can always get swapped out
> > when there's no HTTP requests.... Try doing *that* with Apache. :)
>
> One thing I see is companies using a fu ll blown app server for tiny web
> projects. Seems like overkill to me. If you use a web server with
> servlet support, when you are ready for that beast of an app server, you
> can take all you've done with you. :)
Looks like we're going more into what the original poster bargained for =)
EJB is nice I certainly agree, but as alx points out: EJB servers are
either a) at least $10,000 per installation or b) under beta testing or
development. But they are certainly the way to go in the future if you
want to do any seriously heavy server-side development in Java.
I'm writing a course on EJB so if you want any pointers to resources on
them I'd be happy to share.
And there are open source projects in this area too.
. . . Sean.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
