Raptor, Sorry for the *very* late reply. Please see my answers below.
On Mon, 2004-01-19 at 03:17, raptor wrote: > could I put multiple scripts into one PAR. ?. Yes - a PAR file is just a zip file, files can be added either with a normal zip utility or with the "pp" program. > What if one of the script call the other ? And both scripts are inside the PAR file? The easiest thing to do is a script calling methods or functions in a module. To call another script would require the use of Archive::Zip from within the first (somebody correct me if I'm wrong here, I've been a little out of touch lately) > Could I pack several mod_perl/CGI scripts... if yes yes! See Apache::PAR for more information on using PAR with mod_perl enabled servers (including Apache::Registry scripts, perl Apache modules, static content, etc.) For CGI scripts, just generate an executable archive from the script and stick it in the CGI path, although there are limitations to this approach. In any case, for production usage I would suggest using mod_perl and Apache::PAR for performance reasons (and not just because I wrote it. :-) > what I have to do in apache to accomodate scripts name differences.. > i.e. would I have to make some sort of proxy-script which will call the real > scripts.!! If you are using mod_perl this can be handled by Apache::PAR transparently. For CGI, you could use a trick similar to what Apache::PAR does. Internally, Apache::PAR takes any extra path information available and treats it as a path within the archive to search. So if you call /cgi-perl/test.par/tests/test.cgi, Apache::PAR would look for a script named /script/tests/test.cgi within test.par to execute.
