if you use Apache::Reload with a threaded MPM and multiple interpreters,
the modules will be reloaded by each interpreter as they are used, not
every interpreter all at once. similar to 1.x where each child has
its own interpreter, the modules are reloaded as each kid is hit with a
request.
[EMAIL PROTECTED] wrote:
if you use Apache::Reload with a threaded MPM and multiple interpreters,
the modules will be reloaded by each interpreter as they are used, not
every interpreter all at once. similar to 1.x where each child has
its own interpreter, the modules are reloaded as each
On Fri, 12 Apr 2002, Stas Bekman wrote:
But if talk about futuristic Solar variables (perl globals shared
between threads). what if a solar variable is a reference to CODE? Can
this be shared? If so, will reloading this variable in one interpreter
affect others?
even if that would work,
[EMAIL PROTECTED] wrote:
On Fri, 12 Apr 2002, Stas Bekman wrote:
But if talk about futuristic Solar variables (perl globals shared
between threads). what if a solar variable is a reference to CODE? Can
this be shared? If so, will reloading this variable in one interpreter
affect others?
On Thu, 11 Apr 2002, Perrin Harkins wrote:
Does it look you'll be able to get the solar variables idea to work for
those data types?
i had a simple prototype way back that sorta worked for simple scalars,
probably won't take it any further now that there is threads::shared in
5.7.x.
