[haXe] cacheModule and global variables with threads
Daniel Daley
dan at chameleoncode.jp
Mon Jul 2 21:05:14 CEST 2007
Oh I see. So one instance will be created for every thread in
apache's thread pool.
I know this has been discussed lightly before but is there any plan
to port mod_neko to lighttpd? I'm not terribly against apache, but
I've come to appreciate the light footprint and scalability of
lighttpd and am sad that I will lose that when I chose to use haXe.
Thanks again for your time and such a quick response!
--Dan--
On Jul 2, 2007, at 1:21 AM, Nicolas Cannasse wrote:
>> Hi,
>> I'm wondering with the neko.cacheModule fuction (which I assume
>> activates "application mode" of mod_neko) are global variables
>> thread safe? Is there some kind of locking in place that allows
>> variables to be modified from the "entry point" function without
>> race conditions?
>
> In the case the server runs in multithread, one VM is created per
> thread and per request, and each thread have its own cache, so you
> don't have to worry about MT issues.
>
> Best,
> Nicolas
>
> --
> haXe - an open source web programming language
> http://haxe.org
More information about the Haxe
mailing list