I'd second friedo's suggestion. I've typically done this sort of thing by having a daemon/service sitting in the background waiting for a signal to start. Then your web app may simply send the signal. I've done it using many techniques:
Two techniques you can use to let the daemon/service take no CPU:
1) Use a named pipe, where the daemon/service is blocking while reading the pipe. This is handy when you want to send special commands/arguments to the background task.
2) Use a mutex. Simple when you don't have to pass params to the background task.
Two techniques you can use if you don't mind the background daemon/service periodically polling:
1) Use a plaintext file. Web app creates file with specified name, daemon/service starts job when it notices the file appear.
2) Put a particular row in a "misc" table, and daemon simply looks for it's entry to appear.
--roboticus
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.