Re: Understanding check_modules_and_restart and check_modules_no_restart

On Thu, 9 Mar 2006 11:36:23 -0500, "Philip Semanchuk"
<[email protected]> said:
> I'm trying to make sure that I understand the settings 
> check_modules_and_restart and check_modules_no_restart. Here's how I 
> think they work. Any comments/corrections would be appreciated.
> 
> The settings from best to worst performance are:
> 1) check_modules_and_restart == False and check_modules_no_restart == 
> False
> 2) check_modules_and_restart == False and check_modules_no_restart == 
> True
> 3) check_modules_and_restart == True
> 
> These settings control how lazy the programmer can be about whether or 
> not Spyce notices changes. No surprise, maximum laziness matches worst 
> performance. =) Here are the consequences of these settings:
> 1) Spyce doesn't look for changes. If I change stuff, it is up to me to 
> restart Spyce.
> 2) Spyce looks for changed modules at every request. If it finds one, 
> it reloads the module which leaves the programmer exposed to the 
> weaknesses inherent in Python's reload().
> 3) Spyce looks for changed modules at every request or once every 
> second, whichever comes first. If it finds a change, it restarts the 
> server (which runs in a subprocess).
> 
> Is this correct and (more or less) complete?

Entirely correct.

> Also, the comments in spyceconf.py refer to a mysterious 
> "restart_for_modules" setting which is, I guess, 
> check_modules_and_restart. Am I correct?

Also correct.  (Just committed a fix.  Thanks. :)

-J
-- 
C++ is history repeated as tragedy. Java is history repeated as farce.  --Scott McKay



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642