I never intend to connect directly to the machine from the module above. The module above is intended only to be a "processing center" if you will. Let's call this module above module B and the Windows machine module C.
A client, module A, connects to module B and sends a message of value "STK" to module B. Module B accepts the connection, performs pattern matching to determine what kind of message it is and passes it to the appropriate sub, and closes the socket. Then module B should go back to listening after it passes. The module B sub should connect to module C and send the message, then close the connection with C.
In reply to Re^3: Bidirectional Client/Server - to fork or not to fork?
by Anonymous Monk
in thread Bidirectional Client/Server - to fork or not to fork?
by ljamison
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |