I ended up going the unix signal route - once a process starts, it saves its PID to the database.
The process then goes into a while (<>) loop to wait for input (although i might want to change that to something non-blocking later on)
When one process wants to 'speak' to another, it stores the message in the database (could use shared memory or a file for that), looks up the other process' PID, and sends it a SIGUSR1. The other process has a signal handler installed which, when triggered, looks up the data to be received in the database, and does it's thing.
Only thing i'm worried about is race conditions between handling the signal, and waiting for and receiving input, but i think i can reduce the risk of that.

---

---

• 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.