The principal reason it's not "commercial grade" is that it doesn't have SSL or
the robust feature set (non-Java CGI, NTLM challenge/response authentication,
ties into the OS, etc.) provided by a native server like IIS. Without at least
SSL you can't do commercial web serving very well.
For serving up HTML, I'd expect the JWS and the servlet engine to be comparable
if not the same in terms of performance. But the servlet engine won't be
serving HTML unless you've told it to by mapping HTML requests to it (or
application URLs, like /demo/). Otherwise the native web server will handle
them.
Scott Stirling
-----Original Message-----
From: Mike Hogarth [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 12, 2000 12:17 PM
To: [EMAIL PROTECTED]
Subject: jrun web server and web-app content serving
Quick question to the allaire folks on the list. The Jrun Web Server is not
meant to be 'commercial-grade'. However, JRun is a J2EE app server and as such
serves up HTML content from within the webapp directories. I assume that is
commercial grade and not done by the same java class implementing the JWS.
--Mike Hogarth
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.