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.

In reply to Re^2: RPC via mysql when running under websocketd? by schweini
in thread RPC via mysql when running under websocketd? by schweini

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.