This has nothing to do with mod_perl vs cgi
Uhhh... why do you think I asked about that?
Your user-specific data can be saved on the server with a simple database or on clients with cookies
I must have been very unclear. My problems was the size and complexity of my data. It would take time to load it.
SHM access is raw Perl and it's quite fast and easy
SHM works well? Thanks! I've always thought it was generally a bit of a problem (I've only experience with the old sysV). What CPAN-modules do SHM well?
I can accept the SHM costs of (de)serializing, for now. It won't scale to many users or complex data, so I don't know if it is the long time solution.
(Update: Fixed grammar.)
| [reply] |
I was wondering why you made such a point of mentioning mod_perl. The way Perl is executed has nothing to do with the rest of your question, AFAIK.
SHM -- which is still SYSV :) -- works perfectly, and you can access it with no fear as long as it's Write Once, Read Many blocks. There's no need to use a module at all in this case. Even access for others to write is not difficult; you just build a common lock-block of bits (or bytes, if you can afford to be wasteful), which acts like a set of semaphores. No more tricky than file locking.
If you intend Net-wide access, think again about databases. Your CPU + IO time will still be far less than the transmission time.
| [reply] |