On Wednesday, March 8, 2006 5:06 pm, Bas Scheffers <[EMAIL PROTECTED]> wrote:
>Jeremy Henty said:
>> Are [ns_share and nsd_* shared across *all* Tcl interpreters or just
>> those for one virtual host?
> I have always assumed the new "nsv" shared variables are on a per-server
> basis but never i
> Jeremy Henty said:
>> That's exactly why I'm asking all these questions! I'm looking at
>> porting
>> an ACS-based site to virtual hosts and I'm trying to figure out
>> everything
>> that could go wrong.
When virtual hosting was first added to AOLserver, I tested against
OpenACS and running tw
Jeremy Henty said:
> Thanks again to Bas and Dossy! I'm digging through init.tcl to see how
"init.tcl" in modules/tcl isn't actually the "init script" we are talking
about. The file you are looking at is simply the first .tcl file in that
directory that gets loaded, before the others are done. The
Thanks again to Bas and Dossy! I'm digging through init.tcl to see how all
this works. I'm still unclear of the scope of shared stuff like ns_share ,
nsd_* . Are they shared across *all* Tcl interpreters or just those for one
virtual host? What about mutexes? If one virtual host locks a mut
Jeremy Henty said:
> server, which Dossy has made perfectly clear). When a new thread is
> created,
> is it's Tcl interpreter created from scratch by reexecuting the source, or
> is it simply cloned from a preexisting interpreter? (Or a bit of both?)
Neither, it's executing the init script, creat
On 2006.03.07, Jeremy Henty <[EMAIL PROTECTED]> wrote:
> When a new thread is created,
> is it's Tcl interpreter created from scratch by reexecuting the source, or
> is it simply cloned from a preexisting interpreter? (Or a bit of both?)
It is created from scratch by executing the "init scrip
On Tuesday, March 7, 2006 1:30 pm, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
>... The shared library location ... is set to the
>subdirectory "modules/tcl" within [ns_info home], or:
>
>[ns_info home]/modules/tcl
> ...
>Then, there is a per-server Tcl directory ... which is:
>
>[ns_info h
Jeremy Henty said:
> So does the interpret split the modules/tcl code up into "once-only"
> and "per-interpreter" parts? How is this split made? If a Tcl file
> "source"s another file, is that file split too?
I am not the expert on this, but I think it is simply that all procs are
per interpreter
On 2006.03.07, Jeremy Henty <[EMAIL PROTECTED]> wrote:
>
> So does the interpret split the modules/tcl code up into "once-only"
> and "per-interpreter" parts? How is this split made? If a Tcl file
> "source"s another file, is that file split too?
The server has two Tcl directories (or "librar
On Wednesday, March 1, 2006 9:39 pm, Bas Scheffers <[EMAIL PROTECTED]> wrote:
> AOLserver keeps a pool of threads than handle client requests and
> each of these gets a seperate Tcl interpreter assigned. Each virtual
> server has their own pool.
Thanks Bas, that's very helpful.
> The code in
On 28 Feb 2006, at 16:43, Jeremy Henty wrote:
Does this mean that the different virtual hosts can load different
Tcl code at startup? If
so, how is this implemented? Is there a different Tcl interpreter
for each virtual host?
Yes they can, and they do.
AOLserver keeps a pool of threads tha
I've been reading http://panoptic.com/wiki/aolserver/Virtual_Hosting> and
I noticed
that the library parameter seems to be dependent on the server:
# Tcl Configuration
ns_section ns/server/${server}/tcl
ns_param library ${serverroot}/tcl
Does this mean that the different vi
12 matches
Mail list logo
