comment on

Generally stuff made for the Internet will always work on the local host as well. You can set up "Internet" sockets and do IPC that way, just connecting to 'localhost' to do the deed.

Generally, however, if you want to limit your process's interaction to processes running on the local machine, you should consider Unix domain sockets, which work a lot like Internet sockets, but you listen on a special file, and have your other process "connect" to this file.

Both of these options have the added benefit/drawback of being able to serve any type of client that wants to interact with your "server" script, including clients that don't have any business doing this. If this is a problem, you may want to look into shared memory pools or pipes.

The perlipc man page has some great example code.

In reply to RE: by Fastolfe
in thread "Single-machine IPC via sockets" and other things to say in the dark by Hot Pastrami

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.


XP is just a number
	PerlMonks