I can speak to 3) Netscape Enterprise Server 3.62 + WebSphere Application
Server 2.03.
We actually have a number of web servers set up for separate developers.
WAS 2.03 uses the 0.91 JSP specification, which isn't a big problem if you
don't mind using scriptlets (which I don't mind using). WAS 2.03 runs out
of process, which means when we shutdown the webserver we have to kill the
Java process separately. We had to write a process that makes this less
tedious to do. WAS 2.03 has had problems with timing out sessions, so we've
had to add code that will ensure that at least our login sessions, that we
hang off the session object, are removed through our own monitoring. IBM
keeps working out the bugs and each new release is better than the one
before.
Dan
> ----------
> From: Daison Jose[SMTP:[EMAIL PROTECTED]]
> Reply To: Daison Jose
> Sent: Wednesday, November 10, 1999 4:00 AM
> To: [EMAIL PROTECTED]
> Subject: Webserver Comparison
>
> Hi room,
>
> I need some comparison on different servers which will support Servlets
> like
>
> 1) Netscape + Jrun
>
> 2) Netscape
>
> 3) Netscape + Websphere Application Server
>
> 4) IBM HTTP Server + Websphere Application Server
>
> 5) Apache + Websphere Application Server
>
> If this combination supports servlets, How each will be different from the
> other
> in the efficiency.............
>
>
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
