Jörg Walter wrote:
Am Tuesday, 23. September 2003 09:39, schrieb Matt Sergeant:
Is there any value in making the pre-load module a separate module on
CPAN?
Given that Preload.pm essentially only is 10 lines + docs, probably not...
+1 to putting it in the core dist.
-kip
Am Tuesday, 23. September 2003 09:39, schrieb Matt Sergeant:
> Ah yes, now I see why.
>
> In that case I'm +1.
>
> Is there any value in making the pre-load module a separate module on
> CPAN?
Given that Preload.pm essentially only is 10 lines + docs, probably not...
--
CU
Joerg
On 23 Sep 2003, at 8:23, Jörg Walter wrote:
Am Monday, 22. September 2003 23:48, schrieb Matt Sergeant:
On 22 Sep 2003, at 12:05, Jörg Walter wrote:
I have a working, minimal intrusive and documented patch to add
preloading of
compiled XSP pages.
Interesting. Is there no way to automate this better
Am Monday, 22. September 2003 23:48, schrieb Matt Sergeant:
> On 22 Sep 2003, at 12:05, Jörg Walter wrote:
> > I have a working, minimal intrusive and documented patch to add
> > preloading of
> > compiled XSP pages.
>
> Interesting. Is there no way to automate this better - such as
> providing a p
On 22 Sep 2003, at 12:05, Jörg Walter wrote:
I have a working, minimal intrusive and documented patch to add
preloading of
compiled XSP pages.
Interesting. Is there no way to automate this better - such as
providing a path to XSP's you want pre-compiled, and then have them
compiled automatically
Hi!
I have a working, minimal intrusive and documented patch to add preloading of
compiled XSP pages. It appends one line to the XSP perl code, a subroutine
call to tell XSP.pm the true mtime of the page, and it adds that sub to
XSP.pm, which simply enters the given value as $cache->{$key}{mtim
