bad design with
>> unpredictable results. Also, this is not a tomcat-dev question but a
>> tomcat-user issue, so please continue this discussion there (if you
want
>> to continue it at all).
>>
>> Yoav Shapira
>> Millennium Research Informatics
>>
>>
>
racudaMVC - http://barracudamvc.org
--
"Coffee? I could quit anytime, just not today"
> -Original Message-
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 18, 2004 3:57 PM
> To: Tomcat Developers List
> Subjec
>-Original Message-
>From: Christian Cryder [mailto:[EMAIL PROTECTED]
>Sent: Thursday, March 18, 2004 3:53 PM
>To: Tomcat-Dev
>Subject: thread deadlock problem
>
>Hi folks,
>
>I need to know if someone can explain the following behavior:
>
>1. client browser issues
Hi folks,
I need to know if someone can explain the following behavior:
1. client browser issues a request
2. tomcat servlet code starts handling the request...
a. writes an html redirect to the resp, flushes the buffer, etc
b. thread continues processing (writing to a data structure)
3.
