My original post was about how to save state information when there is
an "interruption" by a configuration page (or something like that) in
the normal CGI flow from one page to the next. I wasn't clear on what
I can do from this point of view. I can determine whether to call the
configuration mode based on whether it has been called before, but I
needed a way to save the "state" when a link for manual configuration
occurs. I ended up saving all of my state parameters into a
server-side session object. When I return from configure page, I
simply update those session parameters in the session object and use
the session object for the input to all of my subroutines that need
parameter access. It seems to work well, but I'm still wondering what
other folks have tried.
Sean
On Oct 5, 2004, at 4:59 PM, Bill Jones wrote:
[off list]
I would have the Perl code change itself AFTER the configuration step
is complete and then use a general link method to allow the user or
admin to go back for manual configuration.
This way, if the Perl code flag is 0, say, then you know the config
steps need to be completed - otherwise that $flag wouod equal 1.
HTH;
-Sx-
=====
-Sx-
seeking employment: http://youve-reached-the.endoftheinternet.org/
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
