1995-08-04 01:00:20 -03:00
|
|
|
"""Generic socket server classes.
|
|
|
|
|
|
|
|
This module tries to capture the various aspects of defining a server:
|
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
For socket-based servers:
|
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
- address family:
|
2001-07-24 17:34:08 -03:00
|
|
|
- AF_INET{,6}: IP (Internet Protocol) sockets (default)
|
1998-03-26 17:13:24 -04:00
|
|
|
- AF_UNIX: Unix domain sockets
|
|
|
|
- others, e.g. AF_DECNET are conceivable (see <socket.h>
|
1995-08-04 01:00:20 -03:00
|
|
|
- socket type:
|
1998-03-26 17:13:24 -04:00
|
|
|
- SOCK_STREAM (reliable stream, e.g. TCP)
|
|
|
|
- SOCK_DGRAM (datagrams, e.g. UDP)
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
|
|
|
|
For request-based servers (including socket-based):
|
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
- client address verification before further looking at the request
|
1998-03-26 17:13:24 -04:00
|
|
|
(This is actually a hook for any processing that needs to look
|
|
|
|
at the request before anything else, e.g. logging)
|
1995-08-04 01:00:20 -03:00
|
|
|
- how to handle multiple requests:
|
1998-03-26 17:13:24 -04:00
|
|
|
- synchronous (one request is handled at a time)
|
|
|
|
- forking (each request is handled by a new process)
|
|
|
|
- threading (each request is handled by a new thread)
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
The classes in this module favor the server type that is simplest to
|
|
|
|
write: a synchronous TCP/IP server. This is bad class design, but
|
|
|
|
save some typing. (There's also the issue that a deep class hierarchy
|
|
|
|
slows down method lookups.)
|
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
There are five classes in an inheritance diagram, four of which represent
|
1995-08-04 01:00:20 -03:00
|
|
|
synchronous servers of four types:
|
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
+------------+
|
|
|
|
| BaseServer |
|
|
|
|
+------------+
|
|
|
|
|
|
|
|
|
v
|
1998-03-26 17:13:24 -04:00
|
|
|
+-----------+ +------------------+
|
|
|
|
| TCPServer |------->| UnixStreamServer |
|
|
|
|
+-----------+ +------------------+
|
|
|
|
|
|
|
|
|
v
|
|
|
|
+-----------+ +--------------------+
|
|
|
|
| UDPServer |------->| UnixDatagramServer |
|
|
|
|
+-----------+ +--------------------+
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1997-07-16 13:21:38 -03:00
|
|
|
Note that UnixDatagramServer derives from UDPServer, not from
|
1995-08-04 01:00:20 -03:00
|
|
|
UnixStreamServer -- the only difference between an IP and a Unix
|
|
|
|
stream server is the address family, which is simply repeated in both
|
1997-07-16 13:21:38 -03:00
|
|
|
unix server classes.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
Forking and threading versions of each type of server can be created
|
|
|
|
using the ForkingServer and ThreadingServer mix-in classes. For
|
|
|
|
instance, a threading UDP server class is created as follows:
|
|
|
|
|
1998-03-26 17:13:24 -04:00
|
|
|
class ThreadingUDPServer(ThreadingMixIn, UDPServer): pass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1997-07-16 13:21:38 -03:00
|
|
|
The Mix-in class must come first, since it overrides a method defined
|
2002-11-22 04:08:44 -04:00
|
|
|
in UDPServer! Setting the various member variables also changes
|
|
|
|
the behavior of the underlying server mechanism.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
To implement a service, you must derive a class from
|
|
|
|
BaseRequestHandler and redefine its handle() method. You can then run
|
|
|
|
various versions of the service by combining one of the server classes
|
|
|
|
with your request handler class.
|
|
|
|
|
|
|
|
The request handler class must be different for datagram or stream
|
|
|
|
services. This can be hidden by using the mix-in request handler
|
|
|
|
classes StreamRequestHandler or DatagramRequestHandler.
|
|
|
|
|
|
|
|
Of course, you still have to use your head!
|
|
|
|
|
|
|
|
For instance, it makes no sense to use a forking server if the service
|
|
|
|
contains state in memory that can be modified by requests (since the
|
|
|
|
modifications in the child process would never reach the initial state
|
|
|
|
kept in the parent process and passed to each child). In this case,
|
|
|
|
you can use a threading server, but you will probably have to use
|
|
|
|
locks to avoid two requests that come in nearly simultaneous to apply
|
|
|
|
conflicting changes to the server state.
|
|
|
|
|
|
|
|
On the other hand, if you are building e.g. an HTTP server, where all
|
|
|
|
data is stored externally (e.g. in the file system), a synchronous
|
|
|
|
class will essentially render the service "deaf" while one request is
|
|
|
|
being handled -- which may be for a very long time if a client is slow
|
|
|
|
to reqd all the data it has requested. Here a threading or forking
|
|
|
|
server is appropriate.
|
|
|
|
|
|
|
|
In some cases, it may be appropriate to process part of a request
|
|
|
|
synchronously, but to finish processing in a forked child depending on
|
|
|
|
the request data. This can be implemented by using a synchronous
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
server and doing an explicit fork in the request handler class
|
1995-08-04 01:00:20 -03:00
|
|
|
handle() method.
|
|
|
|
|
|
|
|
Another approach to handling multiple simultaneous requests in an
|
|
|
|
environment that supports neither threads nor fork (or where these are
|
|
|
|
too expensive or inappropriate for the service) is to maintain an
|
|
|
|
explicit table of partially finished requests and to use select() to
|
|
|
|
decide which request to work on next (or whether to handle a new
|
|
|
|
incoming request). This is particularly important for stream services
|
|
|
|
where each client can potentially be connected for a long time (if
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
threads or subprocesses cannot be used).
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
Future work:
|
|
|
|
- Standard classes for Sun RPC (which uses either UDP or TCP)
|
|
|
|
- Standard mix-in classes to implement various authentication
|
|
|
|
and encryption schemes
|
|
|
|
- Standard framework for select-based multiplexing
|
|
|
|
|
|
|
|
XXX Open problems:
|
|
|
|
- What to do with out-of-band data?
|
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
BaseServer:
|
|
|
|
- split generic "request" functionality out into BaseServer class.
|
|
|
|
Copyright (C) 2000 Luke Kenneth Casson Leighton <lkcl@samba.org>
|
|
|
|
|
|
|
|
example: read entries from a SQL database (requires overriding
|
|
|
|
get_request() to return a table entry from the database).
|
|
|
|
entry is processed by a RequestHandlerClass.
|
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
"""
|
|
|
|
|
2001-01-19 12:45:46 -04:00
|
|
|
# Author of the BaseServer patch: Luke Kenneth Casson Leighton
|
1995-08-04 01:00:20 -03:00
|
|
|
|
2001-07-10 08:50:09 -03:00
|
|
|
# XXX Warning!
|
|
|
|
# There is a test suite for this module, but it cannot be run by the
|
|
|
|
# standard regression test.
|
|
|
|
# To run it manually, run Lib/test/test_socketserver.py.
|
|
|
|
|
|
|
|
__version__ = "0.4"
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
|
|
|
|
import socket
|
|
|
|
import sys
|
|
|
|
import os
|
|
|
|
|
2001-01-20 15:54:20 -04:00
|
|
|
__all__ = ["TCPServer","UDPServer","ForkingUDPServer","ForkingTCPServer",
|
|
|
|
"ThreadingUDPServer","ThreadingTCPServer","BaseRequestHandler",
|
2001-07-10 08:50:09 -03:00
|
|
|
"StreamRequestHandler","DatagramRequestHandler",
|
|
|
|
"ThreadingMixIn", "ForkingMixIn"]
|
2001-01-20 15:54:20 -04:00
|
|
|
if hasattr(socket, "AF_UNIX"):
|
|
|
|
__all__.extend(["UnixStreamServer","UnixDatagramServer",
|
|
|
|
"ThreadingUnixStreamServer",
|
|
|
|
"ThreadingUnixDatagramServer"])
|
1995-08-04 01:00:20 -03:00
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
class BaseServer:
|
1995-08-04 01:00:20 -03:00
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
"""Base class for server classes.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
Methods for the caller:
|
|
|
|
|
|
|
|
- __init__(server_address, RequestHandlerClass)
|
|
|
|
- serve_forever()
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
- handle_request() # if you do not use serve_forever()
|
1998-03-26 17:13:24 -04:00
|
|
|
- fileno() -> int # for select()
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
Methods that may be overridden:
|
|
|
|
|
|
|
|
- server_bind()
|
|
|
|
- server_activate()
|
|
|
|
- get_request() -> request, client_address
|
|
|
|
- verify_request(request, client_address)
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
- server_close()
|
1995-08-04 01:00:20 -03:00
|
|
|
- process_request(request, client_address)
|
2001-04-11 01:02:05 -03:00
|
|
|
- close_request(request)
|
1995-08-04 01:00:20 -03:00
|
|
|
- handle_error()
|
|
|
|
|
|
|
|
Methods for derived classes:
|
|
|
|
|
|
|
|
- finish_request(request, client_address)
|
|
|
|
|
|
|
|
Class variables that may be overridden by derived classes or
|
|
|
|
instances:
|
|
|
|
|
|
|
|
- address_family
|
|
|
|
- socket_type
|
2000-05-09 11:53:29 -03:00
|
|
|
- reuse_address
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
Instance variables:
|
|
|
|
|
|
|
|
- RequestHandlerClass
|
|
|
|
- socket
|
|
|
|
|
|
|
|
"""
|
|
|
|
|
|
|
|
def __init__(self, server_address, RequestHandlerClass):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Constructor. May be extended, do not override."""
|
|
|
|
self.server_address = server_address
|
|
|
|
self.RequestHandlerClass = RequestHandlerClass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def server_activate(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Called by constructor to activate the server.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1998-03-26 17:13:24 -04:00
|
|
|
May be overridden.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1998-03-26 17:13:24 -04:00
|
|
|
"""
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
pass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def serve_forever(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Handle one request at a time until doomsday."""
|
|
|
|
while 1:
|
|
|
|
self.handle_request()
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
# The distinction between handling, getting, processing and
|
|
|
|
# finishing a request is fairly arbitrary. Remember:
|
|
|
|
#
|
|
|
|
# - handle_request() is the top-level call. It calls
|
|
|
|
# get_request(), verify_request() and process_request()
|
|
|
|
# - get_request() is different for stream or datagram sockets
|
|
|
|
# - process_request() is the place that may fork a new process
|
|
|
|
# or create a new thread to finish the request
|
|
|
|
# - finish_request() instantiates the request handler class;
|
|
|
|
# this constructor will handle the request all by itself
|
|
|
|
|
|
|
|
def handle_request(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Handle one request, possibly blocking."""
|
1999-06-15 19:25:32 -03:00
|
|
|
try:
|
|
|
|
request, client_address = self.get_request()
|
|
|
|
except socket.error:
|
|
|
|
return
|
1998-03-26 17:13:24 -04:00
|
|
|
if self.verify_request(request, client_address):
|
|
|
|
try:
|
|
|
|
self.process_request(request, client_address)
|
|
|
|
except:
|
|
|
|
self.handle_error(request, client_address)
|
2001-07-10 08:50:09 -03:00
|
|
|
self.close_request(request)
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def verify_request(self, request, client_address):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Verify the request. May be overridden.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
2002-04-04 18:55:58 -04:00
|
|
|
Return True if we should proceed with this request.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1998-03-26 17:13:24 -04:00
|
|
|
"""
|
2002-04-04 18:55:58 -04:00
|
|
|
return True
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def process_request(self, request, client_address):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Call finish_request.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1998-03-26 17:13:24 -04:00
|
|
|
Overridden by ForkingMixIn and ThreadingMixIn.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1998-03-26 17:13:24 -04:00
|
|
|
"""
|
|
|
|
self.finish_request(request, client_address)
|
2001-07-10 08:50:09 -03:00
|
|
|
self.close_request(request)
|
1995-08-04 01:00:20 -03:00
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
def server_close(self):
|
|
|
|
"""Called to clean-up the server.
|
|
|
|
|
|
|
|
May be overridden.
|
|
|
|
|
|
|
|
"""
|
|
|
|
pass
|
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
def finish_request(self, request, client_address):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Finish one request by instantiating RequestHandlerClass."""
|
|
|
|
self.RequestHandlerClass(request, client_address, self)
|
1995-08-04 01:00:20 -03:00
|
|
|
|
2001-04-11 01:02:05 -03:00
|
|
|
def close_request(self, request):
|
|
|
|
"""Called to clean up an individual request."""
|
|
|
|
pass
|
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
def handle_error(self, request, client_address):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Handle an error gracefully. May be overridden.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1998-03-26 17:13:24 -04:00
|
|
|
The default is to print a traceback and continue.
|
1995-08-04 01:00:20 -03:00
|
|
|
|
1998-03-26 17:13:24 -04:00
|
|
|
"""
|
|
|
|
print '-'*40
|
|
|
|
print 'Exception happened during processing of request from',
|
|
|
|
print client_address
|
|
|
|
import traceback
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
traceback.print_exc() # XXX But this goes to stderr!
|
1998-03-26 17:13:24 -04:00
|
|
|
print '-'*40
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
class TCPServer(BaseServer):
|
|
|
|
|
|
|
|
"""Base class for various socket-based server classes.
|
|
|
|
|
|
|
|
Defaults to synchronous IP stream (i.e., TCP).
|
|
|
|
|
|
|
|
Methods for the caller:
|
|
|
|
|
|
|
|
- __init__(server_address, RequestHandlerClass)
|
|
|
|
- serve_forever()
|
|
|
|
- handle_request() # if you don't use serve_forever()
|
|
|
|
- fileno() -> int # for select()
|
|
|
|
|
|
|
|
Methods that may be overridden:
|
|
|
|
|
|
|
|
- server_bind()
|
|
|
|
- server_activate()
|
|
|
|
- get_request() -> request, client_address
|
|
|
|
- verify_request(request, client_address)
|
|
|
|
- process_request(request, client_address)
|
2001-04-11 01:02:05 -03:00
|
|
|
- close_request(request)
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
- handle_error()
|
|
|
|
|
|
|
|
Methods for derived classes:
|
|
|
|
|
|
|
|
- finish_request(request, client_address)
|
|
|
|
|
|
|
|
Class variables that may be overridden by derived classes or
|
|
|
|
instances:
|
|
|
|
|
|
|
|
- address_family
|
|
|
|
- socket_type
|
|
|
|
- request_queue_size (only for stream sockets)
|
2003-10-09 19:44:05 -03:00
|
|
|
- allow_reuse_address
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
|
|
|
|
Instance variables:
|
|
|
|
|
|
|
|
- server_address
|
|
|
|
- RequestHandlerClass
|
|
|
|
- socket
|
|
|
|
|
|
|
|
"""
|
|
|
|
|
|
|
|
address_family = socket.AF_INET
|
|
|
|
|
|
|
|
socket_type = socket.SOCK_STREAM
|
|
|
|
|
|
|
|
request_queue_size = 5
|
|
|
|
|
2002-08-25 13:36:49 -03:00
|
|
|
allow_reuse_address = False
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
|
|
|
|
def __init__(self, server_address, RequestHandlerClass):
|
|
|
|
"""Constructor. May be extended, do not override."""
|
|
|
|
BaseServer.__init__(self, server_address, RequestHandlerClass)
|
|
|
|
self.socket = socket.socket(self.address_family,
|
|
|
|
self.socket_type)
|
|
|
|
self.server_bind()
|
|
|
|
self.server_activate()
|
|
|
|
|
|
|
|
def server_bind(self):
|
|
|
|
"""Called by constructor to bind the socket.
|
|
|
|
|
|
|
|
May be overridden.
|
|
|
|
|
|
|
|
"""
|
|
|
|
if self.allow_reuse_address:
|
|
|
|
self.socket.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
|
|
|
|
self.socket.bind(self.server_address)
|
|
|
|
|
|
|
|
def server_activate(self):
|
|
|
|
"""Called by constructor to activate the server.
|
|
|
|
|
|
|
|
May be overridden.
|
|
|
|
|
|
|
|
"""
|
|
|
|
self.socket.listen(self.request_queue_size)
|
|
|
|
|
|
|
|
def server_close(self):
|
|
|
|
"""Called to clean-up the server.
|
|
|
|
|
|
|
|
May be overridden.
|
|
|
|
|
|
|
|
"""
|
|
|
|
self.socket.close()
|
|
|
|
|
|
|
|
def fileno(self):
|
|
|
|
"""Return socket file number.
|
|
|
|
|
|
|
|
Interface required by select().
|
|
|
|
|
|
|
|
"""
|
|
|
|
return self.socket.fileno()
|
|
|
|
|
|
|
|
def get_request(self):
|
|
|
|
"""Get the request and client address from the socket.
|
|
|
|
|
|
|
|
May be overridden.
|
|
|
|
|
|
|
|
"""
|
|
|
|
return self.socket.accept()
|
|
|
|
|
2001-04-11 01:02:05 -03:00
|
|
|
def close_request(self, request):
|
|
|
|
"""Called to clean up an individual request."""
|
|
|
|
request.close()
|
|
|
|
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
class UDPServer(TCPServer):
|
|
|
|
|
|
|
|
"""UDP server class."""
|
|
|
|
|
2002-08-25 13:36:49 -03:00
|
|
|
allow_reuse_address = False
|
SF Patch #102980, by Luke Kenneth Casson Leighton: BaseServer class
for SocketServer.py (inherited by TCPServer)
Luke wrote:
The socketserver code, with a little bit of tweaking, can be made
sufficiently general to service "requests" of any kind, not just by sockets.
The BaseServer class was created, for example, to poll a table in a MYSQL
database every 2 seconds. each entry in the table can be allocated a
Handler which deals with the entry.
With this patch, using BaseServer and ThreadedServer classes, the creation
of the server that reads and handles MySQL table entries instead of a
socket was utterly trivial: about 50 lines of python code.
You may consider this code to be utterly useless [why would anyone else
want to do anything like this???] - you are entitled to your opinion. if you
think so, then think of this: have you considered how to cleanly add SSL to
the TCPSocketServer? What about using shared memory as the
communications mechanism for a server, instead of sockets? What about
communication using files?
The SocketServer code is extremely good every useful. it's just that as it
stands, it is tied to sockets, which is not as useful.
I heartily approve of this idea.
2001-01-18 20:44:41 -04:00
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
socket_type = socket.SOCK_DGRAM
|
|
|
|
|
|
|
|
max_packet_size = 8192
|
|
|
|
|
|
|
|
def get_request(self):
|
1998-06-15 23:27:33 -03:00
|
|
|
data, client_addr = self.socket.recvfrom(self.max_packet_size)
|
|
|
|
return (data, self.socket), client_addr
|
|
|
|
|
|
|
|
def server_activate(self):
|
|
|
|
# No need to call listen() for UDP.
|
|
|
|
pass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
2001-04-11 01:02:05 -03:00
|
|
|
def close_request(self, request):
|
|
|
|
# No need to close anything.
|
|
|
|
pass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
class ForkingMixIn:
|
|
|
|
|
|
|
|
"""Mix-in class to handle each request in a new process."""
|
|
|
|
|
|
|
|
active_children = None
|
1999-07-28 18:39:28 -03:00
|
|
|
max_children = 40
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def collect_children(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Internal routine to wait for died children."""
|
|
|
|
while self.active_children:
|
1999-07-28 18:39:28 -03:00
|
|
|
if len(self.active_children) < self.max_children:
|
|
|
|
options = os.WNOHANG
|
|
|
|
else:
|
|
|
|
# If the maximum number of children are already
|
|
|
|
# running, block while waiting for a child to exit
|
|
|
|
options = 0
|
1999-06-17 12:41:33 -03:00
|
|
|
try:
|
1999-07-28 18:39:28 -03:00
|
|
|
pid, status = os.waitpid(0, options)
|
1999-06-17 12:41:33 -03:00
|
|
|
except os.error:
|
|
|
|
pid = None
|
1998-03-26 17:13:24 -04:00
|
|
|
if not pid: break
|
|
|
|
self.active_children.remove(pid)
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def process_request(self, request, client_address):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Fork a new subprocess to process the request."""
|
|
|
|
self.collect_children()
|
|
|
|
pid = os.fork()
|
|
|
|
if pid:
|
|
|
|
# Parent process
|
|
|
|
if self.active_children is None:
|
|
|
|
self.active_children = []
|
|
|
|
self.active_children.append(pid)
|
2001-07-10 08:50:09 -03:00
|
|
|
self.close_request(request)
|
1998-03-26 17:13:24 -04:00
|
|
|
return
|
|
|
|
else:
|
|
|
|
# Child process.
|
|
|
|
# This must never return, hence os._exit()!
|
|
|
|
try:
|
|
|
|
self.finish_request(request, client_address)
|
|
|
|
os._exit(0)
|
|
|
|
except:
|
|
|
|
try:
|
2001-07-10 08:50:09 -03:00
|
|
|
self.handle_error(request, client_address)
|
1998-03-26 17:13:24 -04:00
|
|
|
finally:
|
|
|
|
os._exit(1)
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
|
|
|
|
class ThreadingMixIn:
|
|
|
|
"""Mix-in class to handle each request in a new thread."""
|
|
|
|
|
2002-11-22 04:08:44 -04:00
|
|
|
# Decides how threads will act upon termination of the
|
|
|
|
# main process
|
2002-11-22 10:22:49 -04:00
|
|
|
daemon_threads = False
|
2002-11-22 04:08:44 -04:00
|
|
|
|
2001-10-18 15:02:07 -03:00
|
|
|
def process_request_thread(self, request, client_address):
|
2001-10-23 18:42:45 -03:00
|
|
|
"""Same as in BaseServer but as a thread.
|
|
|
|
|
|
|
|
In addition, exception handling is done here.
|
|
|
|
|
|
|
|
"""
|
|
|
|
try:
|
|
|
|
self.finish_request(request, client_address)
|
|
|
|
self.close_request(request)
|
|
|
|
except:
|
|
|
|
self.handle_error(request, client_address)
|
|
|
|
self.close_request(request)
|
2001-10-18 15:02:07 -03:00
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
def process_request(self, request, client_address):
|
1998-03-26 17:13:24 -04:00
|
|
|
"""Start a new thread to process the request."""
|
1999-10-12 13:20:13 -03:00
|
|
|
import threading
|
2001-10-18 15:02:07 -03:00
|
|
|
t = threading.Thread(target = self.process_request_thread,
|
1999-10-12 13:20:13 -03:00
|
|
|
args = (request, client_address))
|
2002-11-22 04:08:44 -04:00
|
|
|
if self.daemon_threads:
|
|
|
|
t.setDaemon (1)
|
1999-10-12 13:20:13 -03:00
|
|
|
t.start()
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
|
|
|
|
class ForkingUDPServer(ForkingMixIn, UDPServer): pass
|
|
|
|
class ForkingTCPServer(ForkingMixIn, TCPServer): pass
|
|
|
|
|
|
|
|
class ThreadingUDPServer(ThreadingMixIn, UDPServer): pass
|
|
|
|
class ThreadingTCPServer(ThreadingMixIn, TCPServer): pass
|
|
|
|
|
1998-11-30 11:07:01 -04:00
|
|
|
if hasattr(socket, 'AF_UNIX'):
|
|
|
|
|
|
|
|
class UnixStreamServer(TCPServer):
|
|
|
|
address_family = socket.AF_UNIX
|
|
|
|
|
|
|
|
class UnixDatagramServer(UDPServer):
|
|
|
|
address_family = socket.AF_UNIX
|
|
|
|
|
|
|
|
class ThreadingUnixStreamServer(ThreadingMixIn, UnixStreamServer): pass
|
|
|
|
|
|
|
|
class ThreadingUnixDatagramServer(ThreadingMixIn, UnixDatagramServer): pass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
class BaseRequestHandler:
|
|
|
|
|
|
|
|
"""Base class for request handler classes.
|
|
|
|
|
|
|
|
This class is instantiated for each request to be handled. The
|
|
|
|
constructor sets the instance variables request, client_address
|
|
|
|
and server, and then calls the handle() method. To implement a
|
|
|
|
specific service, all you need to do is to derive a class which
|
|
|
|
defines a handle() method.
|
|
|
|
|
|
|
|
The handle() method can find the request as self.request, the
|
1998-11-16 15:06:30 -04:00
|
|
|
client address as self.client_address, and the server (in case it
|
1995-08-04 01:00:20 -03:00
|
|
|
needs access to per-server information) as self.server. Since a
|
|
|
|
separate instance is created for each request, the handle() method
|
|
|
|
can define arbitrary other instance variariables.
|
|
|
|
|
|
|
|
"""
|
|
|
|
|
|
|
|
def __init__(self, request, client_address, server):
|
1998-03-26 17:13:24 -04:00
|
|
|
self.request = request
|
|
|
|
self.client_address = client_address
|
|
|
|
self.server = server
|
|
|
|
try:
|
|
|
|
self.setup()
|
|
|
|
self.handle()
|
|
|
|
self.finish()
|
|
|
|
finally:
|
|
|
|
sys.exc_traceback = None # Help garbage collection
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def setup(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
pass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def handle(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
pass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def finish(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
pass
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
|
|
|
|
# The following two classes make it possible to use the same service
|
|
|
|
# class for stream or datagram servers.
|
|
|
|
# Each class sets up these instance variables:
|
|
|
|
# - rfile: a file object from which receives the request is read
|
|
|
|
# - wfile: a file object to which the reply is written
|
|
|
|
# When the handle() method returns, wfile is flushed properly
|
|
|
|
|
|
|
|
|
|
|
|
class StreamRequestHandler(BaseRequestHandler):
|
|
|
|
|
|
|
|
"""Define self.rfile and self.wfile for stream sockets."""
|
|
|
|
|
2000-09-01 00:25:14 -03:00
|
|
|
# Default buffer sizes for rfile, wfile.
|
|
|
|
# We default rfile to buffered because otherwise it could be
|
|
|
|
# really slow for large data (a getc() call per byte); we make
|
|
|
|
# wfile unbuffered because (a) often after a write() we want to
|
|
|
|
# read and we need to flush the line; (b) big writes to unbuffered
|
|
|
|
# files are typically optimized by stdio even when big reads
|
|
|
|
# aren't.
|
|
|
|
rbufsize = -1
|
|
|
|
wbufsize = 0
|
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
def setup(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
self.connection = self.request
|
2000-09-01 00:25:14 -03:00
|
|
|
self.rfile = self.connection.makefile('rb', self.rbufsize)
|
|
|
|
self.wfile = self.connection.makefile('wb', self.wbufsize)
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def finish(self):
|
2003-01-01 23:07:48 -04:00
|
|
|
if not self.wfile.closed:
|
|
|
|
self.wfile.flush()
|
1998-04-03 12:49:52 -04:00
|
|
|
self.wfile.close()
|
|
|
|
self.rfile.close()
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
|
|
|
|
class DatagramRequestHandler(BaseRequestHandler):
|
|
|
|
|
2001-07-10 08:50:09 -03:00
|
|
|
# XXX Regrettably, I cannot get this working on Linux;
|
|
|
|
# s.recvfrom() doesn't return a meaningful client address.
|
|
|
|
|
1995-08-04 01:00:20 -03:00
|
|
|
"""Define self.rfile and self.wfile for datagram sockets."""
|
|
|
|
|
|
|
|
def setup(self):
|
1998-03-26 17:13:24 -04:00
|
|
|
import StringIO
|
|
|
|
self.packet, self.socket = self.request
|
|
|
|
self.rfile = StringIO.StringIO(self.packet)
|
2002-04-14 21:36:48 -03:00
|
|
|
self.wfile = StringIO.StringIO()
|
1995-08-04 01:00:20 -03:00
|
|
|
|
|
|
|
def finish(self):
|
1998-06-15 23:27:33 -03:00
|
|
|
self.socket.sendto(self.wfile.getvalue(), self.client_address)
|