Inventor wrote:
[snip Apache tragedy]
My program accesses small text configuration files, allowing the user to change them with a CGI interface before writing them out and doing its compute thing. The problem is that each user needs to have their own set of configuration files so that the users don't all step on each other's configuration. I would like for each user to be able to return again and again and always find their configuration files still on the server, eagerly awaiting their chance to be accessed yet again. I imagine I need some sort of authentication system, but the prospect of writing one seems daunting. Are there any modules for doing that? I looked on CPAN and didn't find much of anything obvious. Should I make copies of the files with username.config.txt or something like that? What is the best way to do the copying in Perl? Do you have any thoughts or suggestions about how to set this up properly? I'm kind of uncertain about how to proceed.
It sounds like cookies will do what you want? That way the configuration is stored on the client machine and your CGI code doesn't have to worry about keeping track of the information. You don't even need an authentication system unless you need better security. Rob -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
