Message1869

Author rluse
Recipients
Date 2008-01-04.07:47:57
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Hi,

I'll be posting notes about this bug in another message, but first just
wanted to point out that the example code is a little confusing.

The UDP socket is created and bound to port 5555, but messages are sent to
port 5556. Which means that, in the code given at least, nothing is reading
the messages sent. Is that your intention?

I will assume for now that this is indeed your intention, and that the
example code is a cut down version of a larger piece of code that perhaps
uses a pair of sockets for a 2-way conversation between port 5555 and port
5556.

Hi Alan,

I can't speak for the originator of this problem, but when I reduced his code to something that I understood, (the problem as I see it anyway), happens when the UDP socket is bound and listening for messages and then sends to any other socket.  Indeed a port will probably not send a message to itself.  In my tests, it worked just fine in Java, marginally worked in Python, and completely hung in Jython.  The example given is strange, but it seems to me that it should work, regardless.  So, as far as I am concerned, your assumption is correct.   

 - Bob
History
Date User Action Args
2008-02-20 17:18:00adminlinkissue1782548 messages
2008-02-20 17:18:00admincreate