I read the data via the relative $ENV variable.
Thank You
Linn White
"Roderich Schupp
(ext)" To: "Linn White" <[EMAIL
PROTECTED]>, <[email protected]>
<Roderich.Schupp.ex cc:
[EMAIL PROTECTED]> bcc:
Subject: RE: Caching
additional files
03/30/2006 11:32 AM
> The parl.exe executable is stored on the local users pc. The
> .par file is
> stored on the network drive. Due to security issues, .exe
> files are not
> allowed on the network drive.
> The files are being cached on the local users pc under
> c:\documents and
> settings\{user}\local setttings\temp\par-{user}
I did a little experiment. The cached files are actually under
...\par-{user}\cache-{some sha1 checksum}
However, the checksum doesn't seem to depend on the PAR archive
_at all_ (turns out its the cached checksum of parl.exe itself).
So that would explain if neither changes to the scripts and modules
nor the data files in the PAR would be seen by users that
already have run parl once. And that's what I see on Solaris.
But I can confirm your problem on Windows: changes in scripts
and modules are recognized, while changes to data files are not.
The reason seems to be that scripts and modules are always
loaded from the PAR file (which is uptodate), while data files
are read from the cache (which is not updated because of the
checksum glitch). How do you access the data: by reading
from files (relative to $ENV{PAR_TEMP}/inc) or by using
PAR methods?
Cheers, Roderich
