"Port" to me suggests some sort of system resource, whereas "Listener" at least connotes something is being *done*. If indeed, we are talking about a class whose responsibility it is to receive requests and handle them, then a more active name such as "Listener" (or even "server") might be more appropriate.
-----Original Message----- From: twisted-python-admin@twistedmatrix.com [mailto:twisted-python-admin@twistedmatrix.com]On Behalf Of Moshe Zadka Sent: Monday, July 30, 2001 10:55 PM To: twisted-python@twistedmatrix.com Cc: twisted-python@twistedmatrix.com Subject: Re: [Twisted-Python] "Ports" vs. "Listeners"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 30 Jul 2001, Glyph Lefkowitz glyph@twistedmatrix.com wrote:
"ServerSocket" probably makes the most sense... but then it would make sense to change everything around to sound more like the java.net classnames.
ServerSocket is the official Pythonic name, as in "the ServerSocket module". - -- gpg --keyserver keyserver.pgp.com --recv-keys 46D01BD6 54C4E1FE Secure (inaccessible): 4BD1 7705 EEC0 260A 7F21 4817 C7FC A636 46D0 1BD6 Insecure (accessible): C5A5 A8FA CA39 AB03 10B8 F116 1713 1BCF 54C4 E1FE Learn Python! http://www.ibiblio.org/obp/thinkCSpy
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python