Re: [Text-forge-devel] Text::Forge and PAR

[Aaron P. <aar...@sp...>]

On Sunday, August 10, 2003, at 12:20 PM, Maurice Aubrey wrote:
>

[snip]

>   par:file:/path/to/my/archive.par!templates/
>
> That seems consistent with the JAR URL syntax. With this example, any 
> includes with relative paths would be checked for under templates/ in 
> the PAR.
>
> Alternatively, you could always specify the absolute path directly 
> like this:
>
>   $forge->include('par:file/path/to/my/archive.par!/templates/foo.tf');
>
> Then, to allow this to be used with Apache::PAR, you'd add a ForgeINC 
> to the web.conf file:
>
>   ForgeINC ##PARFILE##/
>
> Thoughts?

I think another thing that might be cool, is to have text forge fetch 
the file depending on the URL provided.  For instance 
par:https://foo.com/archive.par!/templates would fetch the par file to 
use over https (other possibilities would be nfs, webdav, etc).  Also, 
possibly caching the archive on startup.  That would make deploying 
your archive pretty darn easy, just restart apache to re-read the 
archive.  Of course it would also make a single point of failure, and 
possibly be susceptible to man in the middle attacks, but it sure would 
be cool.

What do you think?

--Aaron