Howdy, >1. Implement my engine in Tomcat JVM. >2. Implement it in a JVM outside Tomcat and communicate with the webapp >only >thru DB. > (so almost have 2 independent apps that use the same DB) >3. Implement it in a JVM outside Tomcat and communicate with Tomcat JVM >thru >RMI. > >I like 1. because all would be in one place, and I would use DB connection >pooling provided >by Tomcat.
It's also good because you will be able to easily monitor and manage the DB threads via a web interface if you'd like. >I like 2. because I understand it is bad to open new threads in Tomcat. You understand incorrectly. It's not bad to start new threads in tomcat. It's bad to start badly-written threads. When you use your own threads, either make them daemons or make sure they terminate properly when your webapp shuts down. The performance overhead of creating and running 7 threads is negligible on a modern machine and JVM. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
