Hello and thanks for your reply! Unfortunately, the peer I'm connecting to is proprietary software and it can't be changed, unfortunately. The way I described it is the way in which the peer expects to communicate.
When I connect to the peer on port 8001, I send a message (MESG) and get an ACK reply (with code RESP). After the MESG and RESP are sent/received, respectively, the peer is designed to initiate a connection to port 8000 and send a STAT notifying of the status of the entry in the database (i.e. for addSomething - if it already existed in the database the STAT would provide the code indicating so).
In reply to Re^2: How to share a non-blocking IO::Socket::INET server/pass "listening" control?
by ljamison
in thread How to share a non-blocking IO::Socket::INET server/pass "listening" control?
by ljamison
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |