on 5/10/02 3:57 PM, "Remy Maucherat" <[EMAIL PROTECTED]> wrote:
> I plan to release Coyote 1.0b9 at the same time as Tomcat 4.0.4 Beta 3 > (enough delays, I'm doing it later this afternoon, hopefully). > > The idea is to have TC 4.0.4b3 be a last beta before final, and Coyote 1.0 > would also be released at the same time. I don't know how much this is > compatible with whatever work still needs to be done in JK2. If it's not, > then Coyote 1.0 will be released later (but obviously, it needs to be before > a 4.1.x Stable release). > > Remy My only semi-major complaint about Coyote (and I told Remy about this in person) is that the container now returns 503 errors until the servlet is started. Before, it would block (not quickly return a 503) until the servlet is finished starting. Remy said it was a result of the new threading that Costin put into things. That said, when the classloader is dumped and reloaded as a result of a resource change, the container (properly) blocks until the servlet is reloaded. Now, why reloading behavior is different than startup behavior, I don't know. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
