Geoff wrote:
>I agree.  And I recommend using the MakeAppWorkDir.py script that 
> can be found in the Webware/bin directory to create a separate 
> working directory, complete with its own config files, etc.  That 
> way, you don't have to modify the Webware directory at all.
> Then you can add your own library directories into the directory 
> that you created with MakeAppWorkDir.py.  So my directory structure 
> looks like this:

I'd argue that this should be Webware's default behaviour.  As part 
of the 0.7 changes I strongly suggest removing the need for 
MakeAppWorkDir.py.  This behaviour should be built in directly.  In 
fact, when the transition is made to distutils it will be necessary 
to do this anyway.

In the experimental redesign I've been working on the config files 
have an option that specifies the working directory for storing all 
temp files in (Errors, Sessions, Caches, etc.) and for all relative 
path calculations.  This doesn't have to be the same dir that your 
servlet's are stored in. When not specified the 'workingDir' option 
defaults to the directory from which the 'webware' launcher script 
run.  It can also be specified as a command line arg to the launcher 
script.  

Currently this 'workingDir' option is global to all 'Applications' 
being run in that process (the redesign code implements a 
multi-application version of WebKit).  It might be desirable to allow 
the temporary working dir for session files, etc. to be specified on 
a per-application basis.

Cheers,
Tavis

_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to