I agree. The transport for a client or server should probally not be generalized to a socket at all. Maybe this calls for the creation of twisted.transport ? I am not familiar much with the twisted codebase, so don't kill me if something like this already exists :) On Fri, Aug 31, 2001 at 01:15:16PM -0400, Itamar wrote:
From tcp.py:
============ class Client(Connection): """A client for TCP (and similiar) sockets. """ def __init__(self, host, port, protocol): """Initialize the client, setting up its socket, and request to connect. """ if host == 'unix': # "port" in this case is really a filename ... ============
That is sooo wrong. What if my computer is named 'unix'? Why does the TCP code deal with files?
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-- python -c "print reduce(lambda x,y: x+y,map(lambda x: chr((23069453891\ 36636418523668102630431981680355427L>>(x*8))&0xFF),xrange(0,19)))"