Message6340

Author amak
Recipients amak, basti1302, otmarhumbel, pekka.klarck, pjenvey
Date 2011-01-23.18:33:48
SpamBayes Score 6.6184773e-09
Marked as misclassified No
Message-id <1295807630.09.0.918967808367.issue1697@psf.upfronthosting.co.za>
In-reply-to
Content
OK, as with all things socket-related, there is a complex picture here, which depends on operating system and version, java version, whether or not the host supports IPv6, and design of the jython socket module, which necessarily uses a mixture of java.net and java.nio calls to implement sockets which can have both synchronous and asynchronous behaviour.

One of the primary problems is this java bug, which effectively prevents the use of IPv6 in jython on Windows version older than Vista, i.e. it affects XP/2003.

NIO channels with IPv6 on Windows
http://bugs.sun.com/view_bug.do?bug_id=6230761

This bug affects jython sockets because of the way that of the way such sockets are created, i.e. using java.nio. This is necessary because it is the only way that jython sockets can have asynchronnous behaviour.

Another problem is that whatever behaviour jython sockets exhibit has to be testable on multiple platforms. See here for where I checked in a "test_socket_ipv6.py" module, which had to be disabled because the test results were too unreliable across platforms.

https://fisheye3.atlassian.com/changelog/jython/?cs=4949

I will write about workarounds in the following messages.
History
Date User Action Args
2011-01-23 18:33:50amaksetmessageid: <1295807630.09.0.918967808367.issue1697@psf.upfronthosting.co.za>
2011-01-23 18:33:50amaksetrecipients: + amak, otmarhumbel, pekka.klarck, pjenvey, basti1302
2011-01-23 18:33:50amaklinkissue1697 messages
2011-01-23 18:33:48amakcreate