Lines Matching full:server
1 """Generic socket server classes.
3 This module tries to capture the various aspects of defining a server:
25 The classes in this module favor the server type that is simplest to
26 write: a synchronous TCP/IP server. This is bad class design, but
49 stream server is the address family, which is simply repeated in both
50 unix server classes.
52 Forking and threading versions of each type of server can be created
54 instance, a threading UDP server class is created as follows:
60 the behavior of the underlying server mechanism.
64 various versions of the service by combining one of the server classes
73 For instance, it makes no sense to use a forking server if the service
77 you can use a threading server, but you will probably have to use
79 conflicting changes to the server state.
81 On the other hand, if you are building e.g. an HTTP server, where all
86 server is appropriate.
91 server and doing an explicit fork in the request handler class
162 """Base class for server classes.
214 """Called by constructor to activate the server.
325 """Called to clean-up the server.
360 """Base class for various socket-based server classes.
434 """Called by constructor to activate the server.
442 """Called to clean-up the server.
482 """UDP server class."""
631 and server, and then calls the handle() method. To implement a
636 client address as self.client_address, and the server (in case it
637 needs access to per-server information) as self.server. Since a
643 def __init__(self, request, client_address, server):
646 self.server = server
