A file can be a nice and simple way of interfacing with a background process. You can just have a deamon process update a file periodically and then you can have access to that info whenever you want. You could even use something like Data::Dumper or YAML to exchange complex data structures.
However, if you have multiple tasks to run and you're already using a database, I would use the database to do the communication. i.e. set up one table where each record is a task (id, status etc) and run one or more deamon processes that poll that table looking for new tasks and update the records as they progress. Or run a single deamon that forks() off new children for each task. Or run all tasks sequentially, it'll all look the same from the CGI process's point of view.
-
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.
|
