This is my point
I'm curious to learn whether I can access the data within leaked memory if I *don't* clean up the old items, particularly across Perl invocations, simply by using the known memory address
Steve
| [reply] |
Woah, bad perl-fu going on there. I can't see it working, at least not in any concievably portable way. The /dev/shm method gives you access at the speed of memory; why try to roll your own?
As an alternate suggestion, if you really do want to code something yourself instead of using the previously suggested CGI::Application::Plugin::Session -- Try using FastCGI. You gain persistence of your program, so you can just use standard Perl variables to store session info.
$,=' ';$\=',';$_=[qw,Just another Perl hacker,];print@$_;
| [reply]
[d/l] |
I'm not clear how FastCGI works in this case. Can you provide a code example?
| [reply] |