I have looked over ActivePerl window quirks, things that don't work, etc. I didn't find anything mentioning socket behaviour (seems forking was a concern, but now "works").
What I'm looking for is something telling me that when two processes are operating on the same socket object, one will block the other (but I can't find that statement). BUT ONLY if you are using ActivePerl (ie. unix/linux is capable of operating on the same object in a forked process).
I understand the concept of the transport layer and am looking for a script that can monitor a port for incoming datagrams and -ALSO- listen to STDIN for user input (think: UDP chat...). Implementing a canned reply in the "recv" functionality works fine, but I'm looking to have the user provide the reply to the incoming datagram..
I hope this clarifies what I'm looking to do. And I hope there is atleast one way to do this with ActivePerl. :)
In reply to Re: Re: UDP bidirectional client
by sbrandt
in thread UDP bidirectional client
by sbrandt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |