You might be falling foul of a restriction in the transport as described in the send(2) manpage:
If the message is too long to pass atomically through the
underlying protocol, the error EMSGSIZE is returned, and
the message is not transmitted.
You might try seeing what value $! is set to in the case of your failure.
/J\
In reply to Re: Problem with non-blocking sockets example from Cookbook - send() vs EWOULDBLOCK
by gellyfish
in thread Problem with non-blocking sockets example from Cookbook - send() vs EWOULDBLOCK
by macdee_2
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |