There are many ways to share data between processes. You
can use a local dbm file. You can use IPC::Shareable.
And so on. But all of the efficient ones have the rather
significant problem that all of the requests in your
series have to come back to the same physical machine.
This does not play well with load balancing.
However one crazy way of doing it is like this. One
machine gets the request and forks off a local server.
Other CGI requests are passed the necessary information to
be able to access this temporary server, which is run in a
persistent process, and then when this server decides the
time is right, it de-instantiates itself. This would be a
lot of work though.
Personally I would just see if you can keep the temporary
state in the database, and just have each individual
request deal with the bit of the state that they need to
handle. But I cannot, of course, offer any guesses on
whether this would work without knowing more details than
you have given us.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|