- They should not touch Request and Response objects
- The should be able to know when the servlet container stops if non-daemon so the jvm may gracefully terminate
- If daemon - have a quick shutdown(or appropriate) since the container may shutdown the moment all threads are done with their service() method (I probably got this wrong, but the spec describes this better)
- High perfomance containers are allowed to "restrict" thread creation
- All of the fun concurrency issues
-Tim
[EMAIL PROTECTED] wrote:
Because the appliction server does this for you. If you interfere by using your own threads you could break stuff... (it's a spec violation too).
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
