|Think about Loose Coupling|
connect() & close()by monktim (Friar)
|on Oct 12, 2004 at 21:16 UTC||Need Help??|
monktim has asked for the wisdom of the Perl Monks concerning the following question:
What are the ramifications of calling connect() for an INET Socket Stream repeated times without calling close()? I was sending messages over a socket and immediately called close() after each send session was done. I found my messages were getting lost. When I ran with a breakpoint on my send() the msgs were delivered!
Next I tried the code with a sleep before the close() and that worked too. Not calling close() at all also worked. I don't wait for an ACK msg from the server, it doesn't send one. The server isn't mine so I can't add the ACK response and close the socket after the ACK.
It looks like I can close the socket before the msg is delivered to the server. When this happens the msg gets lost. Is this in fact what is happening?
How should I handle this? I'm probably going to remove the close() call since the connect() and send() happen less than 100 times an hour. Does that sound reasonable?
Thanks in advance.
janitored by ybiC: Fix typo in nodetitle - s/cose/close/;Update: I'm using Perl 5.6.1 build 631 on Win32. I'm using Socket with tcp and I have output autoflush on.