Issue1191

import socket;socket.IPPROTO_TCP=6 solve the problem, the socket module
behaviour is correct if we set this option

cherrypy 3.1.1 uses socket.IPPROTO_TCP; by defining the constant,
soaplib at the very least is able to run all of its unit tests.

(The cherrypy test suite involves tty, so at the very least that needs
to be looked at - I don't think we want to consider supporting tty too
just yet :)

Constantine defines socket protocol constants in
org.python.constantine.platform.IPProto, so hopefully it should be
straightforward to add.

Added a patch to import the desired ipproto constants from Constantine
(for now just IPPROTO_TCP, not certain if we want to pull all of them in).

Should this be a blocker for RC? Or wait until 2.5.1?

This would also enable Pylons on CherryPy

Fixed in trunk at r6159.

Reopening because we (in particular cherrypy wsgiserver) needs this 
supported for server sockets

Since the Java ServerSocket doesn't support setTcpNoDelay I suppose we'd 
have to delay setting the option until the server accept()s and produces 
a normal Socket object? Then we'd then set no delay on that? blah

Closing this again.

Philips' point about setting client options on server sockets and
propagating them client to 'accept'ed clients is an important one, but
this bug is not the place to discuss it.

I have created a new RFE where this issue can be discussed.

Server sockets do not support client options and propagate them to
'accept'ed client sockets.
http://bugs.jython.org/issue1309