If you only want monodirectional IPC, I'd stick with the socket, but use UDP to send it. One advantage of using sockets is that if you ever want to talk to the long running process from a different box, the code need little or no modification.

You could use shared memory. It depends which OS you are on as to which module you would need, but that's more complicated and unless you are doing lots of high speed comms, unnecessary.

You could use Named Pipes, though I've had some problems using these from Perl on Win32 and you rarely see them mentioned for *nix.

On win32 there are a whole raft of other options including Clipboard, COM, Data Copy, DDE, File Mapping, Mailslots, RPC and doubtless some other on *nix too; but from your description, a socket seems the easiest and most appropriate mechanism. And if you ever needed to move to a different platform, it would be the easiest to port.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: Communicating with a long-running process by BrowserUk
in thread Communicating with a long-running process by Marcello

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.