For completeness, I'll replicate the drawing here, just in case that other resource goes away:

(port 8000) "SEND"    PC1    (port 8010) "RECEIVE"
        |                                |
        v ADD                            ^
        |                                |
(port 8000) "RECEIVE" PC2    (port 8010) "SEND"
[download]

(port 8000) "SEND"    PC1    (port 8010) "RECEIVE"
        |                                |
        ^ ACK                            ^
        |                                |
(port 8000) "RECEIVE" PC2    (port 8010) "SEND"
[download]

(port 8000) "SEND"    PC1    (port 8010) "RECEIVE"
        |                                |
        v                                ^ STAT
        |                                |
(port 8000) "RECEIVE" PC2    (port 8010) "SEND"
[download]

From that diagram resp. my interpretation of it, you don't have "SEND" and "RECEIVE" sockets, but some sockets that are listening for and accepting incoming socket connections, and some sockets that are used to talk to the listening sockets. The listening sockets are listening on port 8000 (PC2) and port 8010 (PC1).

You also use the terms "server" and "client", even though that distinction seems somewhat arbitrary to me because both machines seemm to be able to initiate connections to each other.

I'm not clear on whether your current two programs client.pl and server.pl are running on both machines or whether client.pl only runs on PC1 and server.pl only runs on PC2.

I would conceptually split up the "STAT" part separate from the "ADD" part. You can combine the server parts of both if the general format of an incoming message is the same.

The easiest approach to combine the logic of the listeners and the senders in a single program is to launch for threads, two listener threads and two sender threads, or just two threads if you only need a listener on port 8000 and a sender to port 8010 (PC2) or a listener on port 8010 and a sender to port 8000 (PC1).

The next step would be to look at AnyEvent or IO::Select to manage the writing to sockets and the reading from sockets. AnyEvent gives you callbacks for each socket when it's ready to write more data or when it's ready to read more data.

Personally, I would go with the AnyEvent approach because that avoids race conditions.

Hi Corion, thank you for your insight! Would it be possible to ask for a boilerplate of what you mentioned? I've done some basic work with IO::Socket::INET and what I had tried to do was along the lines of creating an INET socket with client and server using PeerAddr/PeerPort & LocalPort but was never able to accomplish the task. I had previously looked over AnyEvent and IO::Select but was unable to figure out where to start with the type of application I'd use them for. Thank you for any assistance!

I'm not sure I could do better than the documentation that I already linked.

See the EXAMPLE section in IO::Select and AnyEvent::Socket.

Maybe you can ask questions by showing actual code you have which tries to use IO::Select or AnyEvent::Socket or threads and tell us how it fails for you to do what you want.