On Jun 6, 2010, at 4:18 PM, Christopher Armstrong wrote:

... We also don't want to have connectSOCKS ...

Since I basically said that we *did* possibly want listenSerialPort as an alternative to the half-working platform-detection stuff that twisted.internet.serialport does, I do want to draw a distinction here.  Although we might want to have a SOCKS enpdoint, 'connectSOCKS' is something that there is _no_ reason I can see for any reactor to have in the future.  SOCKS is a protocol that is implemented on top of TCP.  If you want a SOCKS endpoint, it doesn't need extra support from the reactor; it can be formulated entirely in terms of TCP endpoints.  Even if you're doing something weird like wrapping a C SOCKS library, that library would almost certainly have platform limitations, and provide you with an object that exposed a file descriptor anyway, so you could use IReactorFDset.

(But, practically speaking, you probably just want to use something like 'socksify' anyway, for outgoing connections.)