One option:
If there's an erro in form 2,
Save the user's form data in some session variables
Then use a META HTTP-EQUIV=Refresh CONTENT=0; URL=/step2 tag to get the
user's browser to redirect.
Then populate the form with the data and error message you saved in his/her
session object.
There are
I am in a bit of a jam. I think the cross-post is necessary since I need
the help of Apache, mod_perl, and PHP developers/users. I apologize for the
length, if you have time, my explanation (at the end) should clarify what I
mean.
Summary
---
I need:
- A perl-enabled web server to run on the
Hey everyone,
It's me again... the persistent telnet mod_perl newbie!
(http://msgs.securepoint.com/cgi-bin/get/apache0205/204.html)
I have implemented my project using persistent telnet connections (one for
each user session accessible throught the session to perform various
functions through
Stas Bekman wrote:
It seems that you are after the same functionality as Apache::DBI, you
want a pool of items that you want to be able to choose from.
Look for threads::shared (perl 5.8.0), just create a shared hash with
keys that you use for the map and the values for the actual
I just found this: http://www.devshed.com/Talk/Books/ProApache/page2.html
On Windows platforms, Apache does not fork; consequently, the directives
for controlling the number of processes or their lifetime have no effect.
Instead, Apache runs as a multi-threaded process
Recall that I am using: