Does this describe the situation? 

_____    _____________          _______________           __________
|PHP|----|Perl script|--------->| Perl "Clent"|           |        |
-----    -------------           |             |           |        |
_____    _____________           |             |           |        |
|PHP|----|Perl script|--------->|             |           |        |
-----    -------------           |              |------->|Remote  |
_____    _____________           |             |           |server  |
|PHP|----|Perl script|--------->|             |           |        |
-----    -------------           |             |           |        |
_____    _____________           |             |           |        |
|PHP|----|Perl script|--------->|             |           |        |
-----    -------------            ---------------           ----------

[download]

Four (to 10) PHP servers, call a perl script (50X/sec) to send something to a Perl "client" that then forwards those messages to a remote server.

The perl "client" receives boolean responses from the remote server. Does it return those responses to the PHP servers?

The Perl "client" is there to prevent the perl script from having to reestablish a connection to the remote server every time. But having the perl script talk to the perl "Client" via socket would just move the problem back a stage, so your hoping that they can communicate via shared memory. The perl script is involved because you don't know if you can do socket communications directly from PHP.

I find it unlikely that starting a new process and establishing a connection to the shared memory will be any faster than (say) connection to a server socket within the perl "client".

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"I'd rather go naked than blow up my ass"

In reply to Re: Constant communication between processes by BrowserUk
in thread Constant communication between processes by citycrew

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.