On Saturday 12 Jun 2010 5:58:57 pm Bert Freudenberg wrote:
When I wrote LatexMorph, I also needed writable+volatile for converting LaTeX code to images quickly on the fly. I didn't want persistent directory because of higher i/o latencies, power drain and/or wear-n-tear risks. Do you see any increased security issues with two repos?
I expect similar situations in code involving dynamic font operations, multimedia codec or inter-process communications. Anyone?
We would have to change the SecurityPlugin on all platforms. I see little benefit to Etoys, but hypothetically, which directories would you like this "volatile" directory to be, on each of our supported platforms?
${TMPDIR:-/tmp} on Unix/Linux/OSX. %TEMP% on Windows. But we could use mktemp calls in SecurityPlugin and launch scripts for portability.
BTW, would you like a separate thread for this?
Subbu
On 12.06.2010, at 17:20, K. K. Subramaniam wrote:
On Saturday 12 Jun 2010 5:58:57 pm Bert Freudenberg wrote:
When I wrote LatexMorph, I also needed writable+volatile for converting LaTeX code to images quickly on the fly. I didn't want persistent directory because of higher i/o latencies, power drain and/or wear-n-tear risks. Do you see any increased security issues with two repos?
I expect similar situations in code involving dynamic font operations, multimedia codec or inter-process communications. Anyone?
We would have to change the SecurityPlugin on all platforms. I see little benefit to Etoys, but hypothetically, which directories would you like this "volatile" directory to be, on each of our supported platforms?
${TMPDIR:-/tmp} on Unix/Linux/OSX. %TEMP% on Windows. But we could use mktemp calls in SecurityPlugin and launch scripts for portability.
BTW, would you like a separate thread for this?
The new thread on vm-dev is enough I think, no need to discuss here further :)
- Bert -
etoys-dev@lists.squeakfoundation.org