----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Hi All,
About 4 months ago we completed development on a web site based on
apache/jserv. This website was written for a government (canadian) ministry
concerned with finding jobs for the local citizenery. The url for this site
is (temporarily) jobbank-gta.a4s.org and will eventually be (it may be now)
jobs4.toronto.on.ca. (I had nothing to do with picking the domain names
;-). From planning to release, the site took about 6 months to build, with
4 developers.
During the development process, our team was particularly impressed with
JServ and thought we would share our appreciation along with the features
that we liked most:
Partitioning Execution Environments. The fact that we were able to
partition execution environments was invaluable. This would have been
particularly useful during development, if we'd realized this was possible
(in all future development, we are making use of this). As it is,
partitioning the execution environments has allowed us to redistribute the
site for additional clients on the same box without fear of bugs caused by
overlapping state. It has made it very easy for us to "white label" it.
Load balancing has been very helpful in maximizing performance. In
addition, we are thrilled by the fact that in future (with this site and one
other that is currently in the planning stages) we will be able to cheaply
increase capacity simply by adding machines, rather then being forced to buy
a larger box.
Access to source (the overwhelming advantage to open source :-). In one
particular instance, we were able to make a small change particular to our
environment in order to maximize performance. (I posted a note at the
time).
Stability. We found jserv to be very stable. After a minimal amount of
use, we were comfortable in ruling out jserv as a possible source of any
errors in our code. We found that JServ was exceptionally stable and once
it was running it didn't once cause us a single problem during development.
I just wanted to pass along our appreciation to the JServ development team
for their efforts developing jserv.
Brian Claus
Application Development Specialist
Corelan Communications
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
