Robert Hicks wrote:
I have all my forms validating. Yay!
Congratulations.
The question I have is what happens after validation?
$self-redirect('index.cgi?rm=show_next_page');
Change that to
return $self-show_next_page();
If you do a full redirect then yes, your CGI parameters
Michael Peters wrote:
Robert Hicks wrote:
I have all my forms validating. Yay!
Congratulations.
The question I have is what happens after validation?
$self-redirect('index.cgi?rm=show_next_page');
Change that to
return $self-show_next_page();
If you do a full redirect then
On Tue, 10 Jan 2006 13:51:29 -0500 Perrin Harkins [EMAIL PROTECTED]
wrote:
The only other easy option appears to be using
CGI::Session::ID::incr.
There is also APR::UUID for mod_perl users, a database sequence, or
another UUID module.
And unless you protect the cookie somehow, users
Strong wrote:
I can't understand why You do not simply use a huge random ids?
How can you generate huge, truly random ids? In a multi-process (even
multi-server) environment, how can you guarantee that they are random without a
huge overhead of communication. That's the problem they were
On Tue, 2006-03-07 at 21:07 +0300, Strong wrote:
On Tue, 10 Jan 2006 13:51:29 -0500 Perrin Harkins [EMAIL PROTECTED]
wrote:
The only other easy option appears to be using
CGI::Session::ID::incr.
There is also APR::UUID for mod_perl users, a database sequence, or
another UUID module.
