Re^3: Shared memory and asynchronous access

Thanks for the reply. IO::Socket::INET was actually one of the first packages I tried (and I tried a lot of them...), but my Mac would systematically deny opening a socket. Sure I could have configured it to go around that but I thought I could find another solution than a network protocol that can always be blocked by some firewall or similar program.
Just to add a little bit of context since it doesn't seem to be clear in my first post, this program I'm writing is meant to be used by anyone without special configuration (if possible).

Comment on Re^3: Shared memory and asynchronous access

Replies are listed 'Best First'.
Re^4: Shared memory and asynchronous access by BrowserUk (Patriarch) on Apr 06, 2017 at 11:36 UTC
my Mac would systematically deny opening a socket. Even non-system ports, (those > 1024) and when used in conjunction with the loopback address (127.0.0.1)? (If so, you can add that as another reason (to the existing couple of hundred) why I'll never buy an Apple product.) With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' 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". The enemy of (IT) success is complexity. In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]
Re^5: Shared memory and asynchronous access by vef445 (Novice) on Apr 06, 2017 at 12:48 UTC
On the loopback address? yes On ports >1024?...I don't remember what I tried... I test and build my application on MacOS, Windows 10 (64 and 32), and Debian (64). MacOS is by far the OS where I meet the least problem to install and use the various Perl packages :)	[reply]