Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 1 | |
Alexandre Vassalotti | ce26195 | 2008-05-12 02:31:37 +0000 | [diff] [blame] | 2 | :mod:`socketserver` --- A framework for network servers |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 3 | ======================================================= |
| 4 | |
Alexandre Vassalotti | ce26195 | 2008-05-12 02:31:37 +0000 | [diff] [blame] | 5 | .. module:: socketserver |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 6 | :synopsis: A framework for network servers. |
| 7 | |
Alexandre Vassalotti | ce26195 | 2008-05-12 02:31:37 +0000 | [diff] [blame] | 8 | The :mod:`socketserver` module simplifies the task of writing network servers. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 9 | |
| 10 | There are four basic server classes: :class:`TCPServer` uses the Internet TCP |
| 11 | protocol, which provides for continuous streams of data between the client and |
| 12 | server. :class:`UDPServer` uses datagrams, which are discrete packets of |
| 13 | information that may arrive out of order or be lost while in transit. The more |
| 14 | infrequently used :class:`UnixStreamServer` and :class:`UnixDatagramServer` |
| 15 | classes are similar, but use Unix domain sockets; they're not available on |
| 16 | non-Unix platforms. For more details on network programming, consult a book |
| 17 | such as |
| 18 | W. Richard Steven's UNIX Network Programming or Ralph Davis's Win32 Network |
| 19 | Programming. |
| 20 | |
| 21 | These four classes process requests :dfn:`synchronously`; each request must be |
| 22 | completed before the next request can be started. This isn't suitable if each |
| 23 | request takes a long time to complete, because it requires a lot of computation, |
| 24 | or because it returns a lot of data which the client is slow to process. The |
| 25 | solution is to create a separate process or thread to handle each request; the |
| 26 | :class:`ForkingMixIn` and :class:`ThreadingMixIn` mix-in classes can be used to |
| 27 | support asynchronous behaviour. |
| 28 | |
| 29 | Creating a server requires several steps. First, you must create a request |
| 30 | handler class by subclassing the :class:`BaseRequestHandler` class and |
| 31 | overriding its :meth:`handle` method; this method will process incoming |
| 32 | requests. Second, you must instantiate one of the server classes, passing it |
| 33 | the server's address and the request handler class. Finally, call the |
| 34 | :meth:`handle_request` or :meth:`serve_forever` method of the server object to |
| 35 | process one or many requests. |
| 36 | |
| 37 | When inheriting from :class:`ThreadingMixIn` for threaded connection behavior, |
| 38 | you should explicitly declare how you want your threads to behave on an abrupt |
| 39 | shutdown. The :class:`ThreadingMixIn` class defines an attribute |
| 40 | *daemon_threads*, which indicates whether or not the server should wait for |
| 41 | thread termination. You should set the flag explicitly if you would like threads |
| 42 | to behave autonomously; the default is :const:`False`, meaning that Python will |
| 43 | not exit until all threads created by :class:`ThreadingMixIn` have exited. |
| 44 | |
| 45 | Server classes have the same external methods and attributes, no matter what |
Georg Brandl | fceab5a | 2008-01-19 20:08:23 +0000 | [diff] [blame] | 46 | network protocol they use. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 47 | |
| 48 | |
| 49 | Server Creation Notes |
| 50 | --------------------- |
| 51 | |
| 52 | There are five classes in an inheritance diagram, four of which represent |
| 53 | synchronous servers of four types:: |
| 54 | |
| 55 | +------------+ |
| 56 | | BaseServer | |
| 57 | +------------+ |
| 58 | | |
| 59 | v |
| 60 | +-----------+ +------------------+ |
| 61 | | TCPServer |------->| UnixStreamServer | |
| 62 | +-----------+ +------------------+ |
| 63 | | |
| 64 | v |
| 65 | +-----------+ +--------------------+ |
| 66 | | UDPServer |------->| UnixDatagramServer | |
| 67 | +-----------+ +--------------------+ |
| 68 | |
| 69 | Note that :class:`UnixDatagramServer` derives from :class:`UDPServer`, not from |
| 70 | :class:`UnixStreamServer` --- the only difference between an IP and a Unix |
| 71 | stream server is the address family, which is simply repeated in both Unix |
| 72 | server classes. |
| 73 | |
| 74 | Forking and threading versions of each type of server can be created using the |
| 75 | :class:`ForkingMixIn` and :class:`ThreadingMixIn` mix-in classes. For instance, |
| 76 | a threading UDP server class is created as follows:: |
| 77 | |
| 78 | class ThreadingUDPServer(ThreadingMixIn, UDPServer): pass |
| 79 | |
| 80 | The mix-in class must come first, since it overrides a method defined in |
| 81 | :class:`UDPServer`. Setting the various member variables also changes the |
| 82 | behavior of the underlying server mechanism. |
| 83 | |
| 84 | To implement a service, you must derive a class from :class:`BaseRequestHandler` |
| 85 | and redefine its :meth:`handle` method. You can then run various versions of |
| 86 | the service by combining one of the server classes with your request handler |
| 87 | class. The request handler class must be different for datagram or stream |
| 88 | services. This can be hidden by using the handler subclasses |
| 89 | :class:`StreamRequestHandler` or :class:`DatagramRequestHandler`. |
| 90 | |
| 91 | Of course, you still have to use your head! For instance, it makes no sense to |
| 92 | use a forking server if the service contains state in memory that can be |
| 93 | modified by different requests, since the modifications in the child process |
| 94 | would never reach the initial state kept in the parent process and passed to |
| 95 | each child. In this case, you can use a threading server, but you will probably |
| 96 | have to use locks to protect the integrity of the shared data. |
| 97 | |
| 98 | On the other hand, if you are building an HTTP server where all data is stored |
| 99 | externally (for instance, in the file system), a synchronous class will |
| 100 | essentially render the service "deaf" while one request is being handled -- |
| 101 | which may be for a very long time if a client is slow to receive all the data it |
| 102 | has requested. Here a threading or forking server is appropriate. |
| 103 | |
| 104 | In some cases, it may be appropriate to process part of a request synchronously, |
| 105 | but to finish processing in a forked child depending on the request data. This |
| 106 | can be implemented by using a synchronous server and doing an explicit fork in |
| 107 | the request handler class :meth:`handle` method. |
| 108 | |
| 109 | Another approach to handling multiple simultaneous requests in an environment |
| 110 | that supports neither threads nor :func:`fork` (or where these are too expensive |
| 111 | or inappropriate for the service) is to maintain an explicit table of partially |
| 112 | finished requests and to use :func:`select` to decide which request to work on |
| 113 | next (or whether to handle a new incoming request). This is particularly |
| 114 | important for stream services where each client can potentially be connected for |
Christian Heimes | dd15f6c | 2008-03-16 00:07:10 +0000 | [diff] [blame] | 115 | a long time (if threads or subprocesses cannot be used). See :mod:`asyncore` for |
| 116 | another way to manage this. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 117 | |
Christian Heimes | 5b5e81c | 2007-12-31 16:14:33 +0000 | [diff] [blame] | 118 | .. XXX should data and methods be intermingled, or separate? |
| 119 | how should the distinction between class and instance variables be drawn? |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 120 | |
| 121 | |
| 122 | Server Objects |
| 123 | -------------- |
| 124 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 125 | .. class:: BaseServer |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 126 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 127 | This is the superclass of all Server objects in the module. It defines the |
| 128 | interface, given below, but does not implement most of the methods, which is |
| 129 | done in subclasses. |
| 130 | |
| 131 | |
| 132 | .. method:: BaseServer.fileno() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 133 | |
| 134 | Return an integer file descriptor for the socket on which the server is |
| 135 | listening. This function is most commonly passed to :func:`select.select`, to |
| 136 | allow monitoring multiple servers in the same process. |
| 137 | |
| 138 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 139 | .. method:: BaseServer.handle_request() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 140 | |
Christian Heimes | dd15f6c | 2008-03-16 00:07:10 +0000 | [diff] [blame] | 141 | Process a single request. This function calls the following methods in |
| 142 | order: :meth:`get_request`, :meth:`verify_request`, and |
| 143 | :meth:`process_request`. If the user-provided :meth:`handle` method of the |
| 144 | handler class raises an exception, the server's :meth:`handle_error` method |
| 145 | will be called. If no request is received within :attr:`self.timeout` |
| 146 | seconds, :meth:`handle_timeout` will be called and :meth:`handle_request` |
| 147 | will return. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 148 | |
| 149 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 150 | .. method:: BaseServer.serve_forever(poll_interval=0.5) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 151 | |
Christian Heimes | dd15f6c | 2008-03-16 00:07:10 +0000 | [diff] [blame] | 152 | Handle requests until an explicit :meth:`shutdown` request. Polls for |
| 153 | shutdown every *poll_interval* seconds. |
| 154 | |
| 155 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 156 | .. method:: BaseServer.shutdown() |
Christian Heimes | dd15f6c | 2008-03-16 00:07:10 +0000 | [diff] [blame] | 157 | |
| 158 | Tells the :meth:`serve_forever` loop to stop and waits until it does. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 159 | |
| 160 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 161 | .. attribute:: BaseServer.address_family |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 162 | |
| 163 | The family of protocols to which the server's socket belongs. |
Alexandre Vassalotti | 5f8ced2 | 2008-05-16 00:03:33 +0000 | [diff] [blame] | 164 | Common examples are :const:`socket.AF_INET` and :const:`socket.AF_UNIX`. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 165 | |
| 166 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 167 | .. attribute:: BaseServer.RequestHandlerClass |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 168 | |
| 169 | The user-provided request handler class; an instance of this class is created |
| 170 | for each request. |
| 171 | |
| 172 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 173 | .. attribute:: BaseServer.server_address |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 174 | |
| 175 | The address on which the server is listening. The format of addresses varies |
| 176 | depending on the protocol family; see the documentation for the socket module |
| 177 | for details. For Internet protocols, this is a tuple containing a string giving |
| 178 | the address, and an integer port number: ``('127.0.0.1', 80)``, for example. |
| 179 | |
| 180 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 181 | .. attribute:: BaseServer.socket |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 182 | |
| 183 | The socket object on which the server will listen for incoming requests. |
| 184 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 185 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 186 | The server classes support the following class variables: |
| 187 | |
Christian Heimes | 5b5e81c | 2007-12-31 16:14:33 +0000 | [diff] [blame] | 188 | .. XXX should class variables be covered before instance variables, or vice versa? |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 189 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 190 | .. attribute:: BaseServer.allow_reuse_address |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 191 | |
| 192 | Whether the server will allow the reuse of an address. This defaults to |
| 193 | :const:`False`, and can be set in subclasses to change the policy. |
| 194 | |
| 195 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 196 | .. attribute:: BaseServer.request_queue_size |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 197 | |
| 198 | The size of the request queue. If it takes a long time to process a single |
| 199 | request, any requests that arrive while the server is busy are placed into a |
| 200 | queue, up to :attr:`request_queue_size` requests. Once the queue is full, |
| 201 | further requests from clients will get a "Connection denied" error. The default |
| 202 | value is usually 5, but this can be overridden by subclasses. |
| 203 | |
| 204 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 205 | .. attribute:: BaseServer.socket_type |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 206 | |
| 207 | The type of socket used by the server; :const:`socket.SOCK_STREAM` and |
Alexandre Vassalotti | 5f8ced2 | 2008-05-16 00:03:33 +0000 | [diff] [blame] | 208 | :const:`socket.SOCK_DGRAM` are two common values. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 209 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 210 | |
| 211 | .. attribute:: BaseServer.timeout |
Georg Brandl | fceab5a | 2008-01-19 20:08:23 +0000 | [diff] [blame] | 212 | |
Christian Heimes | dd15f6c | 2008-03-16 00:07:10 +0000 | [diff] [blame] | 213 | Timeout duration, measured in seconds, or :const:`None` if no timeout is |
| 214 | desired. If :meth:`handle_request` receives no incoming requests within the |
| 215 | timeout period, the :meth:`handle_timeout` method is called. |
Georg Brandl | fceab5a | 2008-01-19 20:08:23 +0000 | [diff] [blame] | 216 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 217 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 218 | There are various server methods that can be overridden by subclasses of base |
| 219 | server classes like :class:`TCPServer`; these methods aren't useful to external |
| 220 | users of the server object. |
| 221 | |
Christian Heimes | 5b5e81c | 2007-12-31 16:14:33 +0000 | [diff] [blame] | 222 | .. XXX should the default implementations of these be documented, or should |
Alexandre Vassalotti | ce26195 | 2008-05-12 02:31:37 +0000 | [diff] [blame] | 223 | it be assumed that the user will look at socketserver.py? |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 224 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 225 | .. method:: BaseServer.finish_request() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 226 | |
| 227 | Actually processes the request by instantiating :attr:`RequestHandlerClass` and |
| 228 | calling its :meth:`handle` method. |
| 229 | |
| 230 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 231 | .. method:: BaseServer.get_request() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 232 | |
| 233 | Must accept a request from the socket, and return a 2-tuple containing the *new* |
| 234 | socket object to be used to communicate with the client, and the client's |
| 235 | address. |
| 236 | |
| 237 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 238 | .. method:: BaseServer.handle_error(request, client_address) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 239 | |
| 240 | This function is called if the :attr:`RequestHandlerClass`'s :meth:`handle` |
| 241 | method raises an exception. The default action is to print the traceback to |
| 242 | standard output and continue handling further requests. |
| 243 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 244 | |
| 245 | .. method:: BaseServer.handle_timeout() |
Georg Brandl | fceab5a | 2008-01-19 20:08:23 +0000 | [diff] [blame] | 246 | |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 247 | This function is called when the :attr:`timeout` attribute has been set to a |
| 248 | value other than :const:`None` and the timeout period has passed with no |
Georg Brandl | fceab5a | 2008-01-19 20:08:23 +0000 | [diff] [blame] | 249 | requests being received. The default action for forking servers is |
| 250 | to collect the status of any child processes that have exited, while |
| 251 | in threading servers this method does nothing. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 252 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 253 | |
| 254 | .. method:: BaseServer.process_request(request, client_address) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 255 | |
| 256 | Calls :meth:`finish_request` to create an instance of the |
| 257 | :attr:`RequestHandlerClass`. If desired, this function can create a new process |
| 258 | or thread to handle the request; the :class:`ForkingMixIn` and |
| 259 | :class:`ThreadingMixIn` classes do this. |
| 260 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 261 | |
Christian Heimes | 5b5e81c | 2007-12-31 16:14:33 +0000 | [diff] [blame] | 262 | .. Is there any point in documenting the following two functions? |
| 263 | What would the purpose of overriding them be: initializing server |
| 264 | instance variables, adding new network families? |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 265 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 266 | .. method:: BaseServer.server_activate() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 267 | |
| 268 | Called by the server's constructor to activate the server. The default behavior |
| 269 | just :meth:`listen`\ s to the server's socket. May be overridden. |
| 270 | |
| 271 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 272 | .. method:: BaseServer.server_bind() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 273 | |
| 274 | Called by the server's constructor to bind the socket to the desired address. |
| 275 | May be overridden. |
| 276 | |
| 277 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 278 | .. method:: BaseServer.verify_request(request, client_address) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 279 | |
| 280 | Must return a Boolean value; if the value is :const:`True`, the request will be |
| 281 | processed, and if it's :const:`False`, the request will be denied. This function |
| 282 | can be overridden to implement access controls for a server. The default |
| 283 | implementation always returns :const:`True`. |
| 284 | |
| 285 | |
| 286 | RequestHandler Objects |
| 287 | ---------------------- |
| 288 | |
| 289 | The request handler class must define a new :meth:`handle` method, and can |
| 290 | override any of the following methods. A new instance is created for each |
| 291 | request. |
| 292 | |
| 293 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 294 | .. method:: RequestHandler.finish() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 295 | |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 296 | Called after the :meth:`handle` method to perform any clean-up actions |
| 297 | required. The default implementation does nothing. If :meth:`setup` or |
| 298 | :meth:`handle` raise an exception, this function will not be called. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 299 | |
| 300 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 301 | .. method:: RequestHandler.handle() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 302 | |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 303 | This function must do all the work required to service a request. The |
| 304 | default implementation does nothing. Several instance attributes are |
| 305 | available to it; the request is available as :attr:`self.request`; the client |
| 306 | address as :attr:`self.client_address`; and the server instance as |
| 307 | :attr:`self.server`, in case it needs access to per-server information. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 308 | |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 309 | The type of :attr:`self.request` is different for datagram or stream |
| 310 | services. For stream services, :attr:`self.request` is a socket object; for |
| 311 | datagram services, :attr:`self.request` is a pair of string and socket. |
| 312 | However, this can be hidden by using the request handler subclasses |
| 313 | :class:`StreamRequestHandler` or :class:`DatagramRequestHandler`, which |
| 314 | override the :meth:`setup` and :meth:`finish` methods, and provide |
| 315 | :attr:`self.rfile` and :attr:`self.wfile` attributes. :attr:`self.rfile` and |
| 316 | :attr:`self.wfile` can be read or written, respectively, to get the request |
| 317 | data or return data to the client. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 318 | |
| 319 | |
Benjamin Peterson | d23f822 | 2009-04-05 19:13:16 +0000 | [diff] [blame] | 320 | .. method:: RequestHandler.setup() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 321 | |
| 322 | Called before the :meth:`handle` method to perform any initialization actions |
| 323 | required. The default implementation does nothing. |
| 324 | |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 325 | |
| 326 | Examples |
| 327 | -------- |
| 328 | |
| 329 | :class:`socketserver.TCPServer` Example |
| 330 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 331 | |
| 332 | This is the server side:: |
| 333 | |
| 334 | import socketserver |
| 335 | |
| 336 | class MyTCPHandler(socketserver.BaseRequestHandler): |
| 337 | """ |
| 338 | The RequestHandler class for our server. |
| 339 | |
| 340 | It is instantiated once per connection to the server, and must |
| 341 | override the handle() method to implement communication to the |
| 342 | client. |
| 343 | """ |
| 344 | |
| 345 | def handle(self): |
| 346 | # self.request is the TCP socket connected to the client |
| 347 | self.data = self.request.recv(1024).strip() |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 348 | print("%s wrote:" % self.client_address[0]) |
| 349 | print(self.data) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 350 | # just send back the same data, but upper-cased |
| 351 | self.request.send(self.data.upper()) |
| 352 | |
| 353 | if __name__ == "__main__": |
| 354 | HOST, PORT = "localhost", 9999 |
| 355 | |
| 356 | # Create the server, binding to localhost on port 9999 |
| 357 | server = socketserver.TCPServer((HOST, PORT), MyTCPHandler) |
| 358 | |
| 359 | # Activate the server; this will keep running until you |
| 360 | # interrupt the program with Ctrl-C |
| 361 | server.serve_forever() |
| 362 | |
| 363 | An alternative request handler class that makes use of streams (file-like |
| 364 | objects that simplify communication by providing the standard file interface):: |
| 365 | |
| 366 | class MyTCPHandler(socketserver.StreamRequestHandler): |
| 367 | |
| 368 | def handle(self): |
| 369 | # self.rfile is a file-like object created by the handler; |
| 370 | # we can now use e.g. readline() instead of raw recv() calls |
| 371 | self.data = self.rfile.readline().strip() |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 372 | print("%s wrote:" % self.client_address[0]) |
| 373 | print(self.data) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 374 | # Likewise, self.wfile is a file-like object used to write back |
| 375 | # to the client |
| 376 | self.wfile.write(self.data.upper()) |
| 377 | |
| 378 | The difference is that the ``readline()`` call in the second handler will call |
| 379 | ``recv()`` multiple times until it encounters a newline character, while the |
| 380 | single ``recv()`` call in the first handler will just return what has been sent |
| 381 | from the client in one ``send()`` call. |
| 382 | |
| 383 | |
| 384 | This is the client side:: |
| 385 | |
| 386 | import socket |
| 387 | import sys |
| 388 | |
| 389 | HOST, PORT = "localhost", 9999 |
| 390 | data = " ".join(sys.argv[1:]) |
| 391 | |
| 392 | # Create a socket (SOCK_STREAM means a TCP socket) |
| 393 | sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM) |
| 394 | |
| 395 | # Connect to server and send data |
| 396 | sock.connect((HOST, PORT)) |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 397 | sock.send(bytes(data + "\n","utf8")) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 398 | |
| 399 | # Receive data from the server and shut down |
| 400 | received = sock.recv(1024) |
| 401 | sock.close() |
| 402 | |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 403 | print("Sent: %s" % data) |
| 404 | print("Received: %s" % received) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 405 | |
| 406 | |
| 407 | The output of the example should look something like this: |
| 408 | |
| 409 | Server:: |
| 410 | |
| 411 | $ python TCPServer.py |
| 412 | 127.0.0.1 wrote: |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 413 | b'hello world with TCP' |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 414 | 127.0.0.1 wrote: |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 415 | b'python is nice' |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 416 | |
| 417 | Client:: |
| 418 | |
| 419 | $ python TCPClient.py hello world with TCP |
| 420 | Sent: hello world with TCP |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 421 | Received: b'HELLO WORLD WITH TCP' |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 422 | $ python TCPClient.py python is nice |
| 423 | Sent: python is nice |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 424 | Received: b'PYTHON IS NICE' |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 425 | |
| 426 | |
| 427 | :class:`socketserver.UDPServer` Example |
| 428 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 429 | |
| 430 | This is the server side:: |
| 431 | |
| 432 | import socketserver |
| 433 | |
| 434 | class MyUDPHandler(socketserver.BaseRequestHandler): |
| 435 | """ |
| 436 | This class works similar to the TCP handler class, except that |
| 437 | self.request consists of a pair of data and client socket, and since |
| 438 | there is no connection the client address must be given explicitly |
| 439 | when sending data back via sendto(). |
| 440 | """ |
| 441 | |
| 442 | def handle(self): |
| 443 | data = self.request[0].strip() |
| 444 | socket = self.request[1] |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 445 | print("%s wrote:" % self.client_address[0]) |
| 446 | print(data) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 447 | socket.sendto(data.upper(), self.client_address) |
| 448 | |
| 449 | if __name__ == "__main__": |
Benjamin Peterson | 39778f6 | 2009-11-25 18:37:12 +0000 | [diff] [blame] | 450 | HOST, PORT = "localhost", 9999 |
| 451 | server = socketserver.UDPServer((HOST, PORT), MyUDPHandler) |
| 452 | server.serve_forever() |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 453 | |
| 454 | This is the client side:: |
| 455 | |
| 456 | import socket |
| 457 | import sys |
| 458 | |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 459 | HOST, PORT = "localhost", 9999 |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 460 | data = " ".join(sys.argv[1:]) |
| 461 | |
| 462 | # SOCK_DGRAM is the socket type to use for UDP sockets |
| 463 | sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) |
| 464 | |
| 465 | # As you can see, there is no connect() call; UDP has no connections. |
| 466 | # Instead, data is directly sent to the recipient via sendto(). |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 467 | sock.sendto(bytes(data + "\n","utf8"), (HOST, PORT)) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 468 | received = sock.recv(1024) |
| 469 | |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 470 | print("Sent: %s" % data) |
| 471 | print("Received: %s" % received) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 472 | |
| 473 | The output of the example should look exactly like for the TCP server example. |
| 474 | |
| 475 | |
| 476 | Asynchronous Mixins |
| 477 | ~~~~~~~~~~~~~~~~~~~ |
| 478 | |
| 479 | To build asynchronous handlers, use the :class:`ThreadingMixIn` and |
| 480 | :class:`ForkingMixIn` classes. |
| 481 | |
| 482 | An example for the :class:`ThreadingMixIn` class:: |
| 483 | |
| 484 | import socket |
| 485 | import threading |
| 486 | import socketserver |
| 487 | |
| 488 | class ThreadedTCPRequestHandler(socketserver.BaseRequestHandler): |
| 489 | |
| 490 | def handle(self): |
| 491 | data = self.request.recv(1024) |
Georg Brandl | f992640 | 2008-06-13 06:32:25 +0000 | [diff] [blame] | 492 | cur_thread = threading.current_thread() |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 493 | response = bytes("%s: %s" % (cur_thread.getName(), data),'ascii') |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 494 | self.request.send(response) |
| 495 | |
| 496 | class ThreadedTCPServer(socketserver.ThreadingMixIn, socketserver.TCPServer): |
| 497 | pass |
| 498 | |
| 499 | def client(ip, port, message): |
| 500 | sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM) |
| 501 | sock.connect((ip, port)) |
| 502 | sock.send(message) |
| 503 | response = sock.recv(1024) |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 504 | print("Received: %s" % response) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 505 | sock.close() |
| 506 | |
| 507 | if __name__ == "__main__": |
| 508 | # Port 0 means to select an arbitrary unused port |
| 509 | HOST, PORT = "localhost", 0 |
| 510 | |
| 511 | server = ThreadedTCPServer((HOST, PORT), ThreadedTCPRequestHandler) |
| 512 | ip, port = server.server_address |
| 513 | |
| 514 | # Start a thread with the server -- that thread will then start one |
| 515 | # more thread for each request |
| 516 | server_thread = threading.Thread(target=server.serve_forever) |
| 517 | # Exit the server thread when the main thread terminates |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 518 | server_thread.setDaemon(True) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 519 | server_thread.start() |
Benjamin Peterson | d75fcb4 | 2009-02-19 04:22:03 +0000 | [diff] [blame] | 520 | print("Server loop running in thread:", server_thread.name) |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 521 | |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 522 | client(ip, port, b"Hello World 1") |
| 523 | client(ip, port, b"Hello World 2") |
| 524 | client(ip, port, b"Hello World 3") |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 525 | |
| 526 | server.shutdown() |
| 527 | |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 528 | |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 529 | The output of the example should look something like this:: |
| 530 | |
| 531 | $ python ThreadedTCPServer.py |
| 532 | Server loop running in thread: Thread-1 |
Benjamin Peterson | 06fd5f8 | 2008-11-08 17:24:34 +0000 | [diff] [blame] | 533 | Received: b"Thread-2: b'Hello World 1'" |
| 534 | Received: b"Thread-3: b'Hello World 2'" |
| 535 | Received: b"Thread-4: b'Hello World 3'" |
Georg Brandl | b533e26 | 2008-05-25 18:19:30 +0000 | [diff] [blame] | 536 | |
| 537 | |
| 538 | The :class:`ForkingMixIn` class is used in the same way, except that the server |
| 539 | will spawn a new process for each request. |