Oh yes, now I understand. Is there some simple way to make the
"response generating" piece of code single-threaded? (Not the whole
sending of the response, just the response generation.) I must say I
am not very familiar with Smalltalk processes.

On Wed, 14 Jul 2004 00:58:36 -0700, Avi Bryant <avi at beta4.com> wrote:
> 
> On Jul 14, 2004, at 12:48 AM, Frantisek Fuka wrote:
> 
> > Either I didn't make my question clear or I am now rather confused by
> > your answer. I thought that the current request is set by using
> > "HttpRequest>>current:" into some sort of global variable and thus
> > there cannot be more than one response being generated at one time,
> > because "HttpRequest current" would then randomly change during the
> > generating of the response. (Of course, after the resulting
> > HttpResponse stream is calculated and starts to be served to the
> > client, there can and will be other requests). Is this not true?
> 
> It's not global to the whole image, only global to the current Process.
>   If there are concurrent requests, there will be many processes running
> at once, and evaluating "HttpRequest current" in each would give a
> different value.
> 
> Avi
> 
> 


-- 
Frantisek Fuka (yes, that IS my real name)
(and it's pronounced "Fran-tjee-shek Foo-kah")
My E-Mail: fuka at fuxoft.cz
My Homepage: http://www.fuxoft.cz
My ICQ UIN: 2745855
FFFILM: http://surf.to/fffilm