Hello all ,
I just cam a cross the PAR module when i was look for a way to combine MY PERL
library for distribution. My first testing with this module was very positief
and i was happy to see that there was also a ModPerl module to use the PAR
modules .
But , reading the slides from Autrijus , i've noticed that he mentioned (slide
11 & 12) that it was possible to return a string with the module code instead
of a file handle so perl can "load" the module and compile it.
I.ve noticed that PAR doesn't do this , it stores the modules in my /tmp
directory and returns a FH from this files.
I was wondering is there are any reasons , except maybe for memory footprint
and caching , to store the data into a file. I's it possible to extract the
data from the ZIP file and return that instead of storing it in to a external
file. This will remove the need for this external file.
The way i see it is that when a include all MY libraries in 1 big zip file ,
it's a little bit crazy to extract them to the /tmp location and us those
files ?
So can we expect for this kind of beheaviour or are there any "NO GO" issues
i'm missing .
greetings,
luc
