On Thursday, January 30, 2003, at 09:25 AM, Puneet Kishor wrote:
A long while back I asked a similar question -- how do I make state management possible with Perl and Apache, specifically on MacOS X, but ideally in a platform independent kind of way. At that time I believe Apache::Sessions was not compatible with OS X. I haven't found any statement now contradicting that.I don't remember any problem with Apache::Session on OS X. It certainly works fine now, I'm using it.
Even if Apache::Sessions did work on OS X, does it _require_ mod_perl? I don't have mod_perl, I don't want to install mod_perl (for now at least), and I certainly don't want to create a solution that _requires_ mod_perl, because the users of my solution may not have mod_perl. Additionally, I don't want to mess with Apple's perl, and as much as possible, I want to use that rather than install my own.The name "Apache::Session" is actually sort of a bad name for it - it doesn't really *require* mod_perl, it's just used most of the time in that context. You could probably get by fine with it.
However, you might be happier just using Cache::Cache instead, if you're not going to do any mod_perl interaction. Some people even use Cache::Cache under mod_perl. Maybe you could see if that fills your needs too.
Is there any easy way to achieve painless state management with perl and Apache? Obviously, I am not wanting to bop values around in the URL, and don't want to depend on cookies.So, uh, where do you propose to put the state information? Since HTTP is stateless, you'll need to put at least a session key in either the URL or a cookie, or submit it as a POST argument with every request (hint: DON'T do that), or something. Otherwise it's not possible.
-Ken
