On 5/24/07, Mark Henry <[EMAIL PROTECTED]> wrote:
what I've
done instead is have a single script, which based on a hidden field in a
form, figures out where execution should resume, and for every re-invocation
of the script, the data structures would (should?) be reloaded anew.
That sounds reas
So, my *new* question is, (and I've got the hardcopy of the mod
perl book so if theres a chapter I need to read, just point it out)
i'd read the book - sit down and spend 2-4 hours skimming through
it. all of your questions are answered in it, and it explains the
architecture much more
All,
Thanks for the helpful replies - I'm totally new to the apache world so
being a bit gun-shy on trying a persistence framework off the bat, what I've
done instead is have a single script, which based on a hidden field in a
form, figures out where execution should resume, and for every re-invo
Mark-
you can not ensure that in-memory structures will be processed by the
same server/child, let alone be available to another script.
You'll need to find an inter-process store for your persistent item
if you're using something that provides for sessions ( ie
Apache::Session ) you can j
Hi,
I've done a decent amount of work in a particular script which reads a
(flatfile) database, builds some data structures (hashes of arrays of
arrays) does some processing and spits out a form.
I then want the user to choose some values on the form, submit it, then I
would act upon that, ultim
