那么webpy是什么呢? 阅读它的源码咱们又能学到什么呢?
简单说webpy就是一个开源的web应用框架(官方首页:http://webpy.org/)
它的源代码很是整洁精干,学习它一方面可让咱们快速了解python语法(遇到看不懂的语法就去google),另外一方面能够学习到python高级特性的使用(譬如反射,装饰器),并且在webpy中还内置了一个简单HTTP服务器(文档建议该服务器仅用于开发环境,生产环境应使用apache之类的),对于想简单了解下HTTP服务器实现的朋友来讲,这个是再好不过的例子了(而且在这个服务器代码中,还能够学习到线程池,消息队列等技术),除此以外webpy还包括模板渲染引擎,DB框架等等,这里面的每个部分均可以单独拿出来学习.
在JavaWeb开发中有Servlet规范,那么Python Web开发中有规范吗?
答案就是:WSGI,它定义了服务器如何与你的webapp交互
关于WSGI规范,能够参看下面这个连接:
http://ivory.idyll.org/articles/wsgi-intro/what-is-wsgi.html
如今咱们利用webpy内置的WSGIServer,按照WSGI规范,写一个简单的webapp,eg: html
- import web.wsgiserver
-
- def my_wsgi_app(env, start_response):
- status = '200 OK'
- response_headers = [('Content-type','text/plain')]
- start_response(status, response_headers)
- return ['Hello world!']
-
- server = web.wsgiserver.CherryPyWSGIServer(("127.0.0.1", 8080), my_wsgi_app);
- server.start()
执行代码:
在具体看WSGIServer代码以前,咱们先看一幅图,这幅图概述了WSGIServer内部执行流程:

接下来咱们看下代码,ps: 为了较清晰的梳理主干流程,我只列出核心代码段 python
- class CherryPyWSGIServer(HTTPServer):
-
- def __init__(self, bind_addr, wsgi_app, numthreads=10, server_name=None,
- max=-1, request_queue_size=5, timeout=10, shutdown_timeout=5):
-
- self.requests = ThreadPool(self, min=numthreads or 1, max=max)
-
- self.wsgi_app = wsgi_app
-
- self.gateway = WSGIGateway_10
-
- self.bind_addr = bind_addr
-
-
- class HTTPServer(object):
-
-
-
- def start(self):
-
-
- if isinstance(self.bind_addr, basestring):
- try: os.unlink(self.bind_addr)
- except: pass
- info = [(socket.AF_UNIX, socket.SOCK_STREAM, 0, "", self.bind_addr)]
- else:
-
- host, port = self.bind_addr
- try:
- info = socket.getaddrinfo(host, port, socket.AF_UNSPEC,
- socket.SOCK_STREAM, 0, socket.AI_PASSIVE)
- except socket.gaierror:
-
-
-
- for res in info:
- af, socktype, proto, canonname, sa = res
- try:
- self.bind(af, socktype, proto)
- except socket.error:
- if self.socket:
- self.socket.close()
- self.socket = None
- continue
- break
- if not self.socket:
- raise socket.error(msg)
-
-
- self.socket.listen(self.request_queue_size)
-
-
- self.requests.start()
-
- self.ready = True
- while self.ready:
-
-
-
- self.tick()
-
- def bind(self, family, type, proto=0):
-
- self.socket = socket.socket(family, type, proto)
-
- self.socket.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
-
- self.socket.bind(self.bind_addr)
-
-
- def tick(self):
- try:
-
- s, addr = self.socket.accept()
-
-
- makefile = CP_fileobject
- conn = self.ConnectionClass(self, s, makefile)
-
- self.requests.put(conn)
- except :
-
以前咱们说过HTTPServer中的request属性是一个线程池(这个线程池内部关联着一个消息队列),如今咱们看看做者是如何实现一个线程池的: web
- class ThreadPool(object):
-
- def __init__(self, server, min=10, max=-1):
-
- self.server = server
-
- self.min = min
- self.max = max
-
- self._threads = []
-
- self._queue = Queue.Queue()
-
-
-
- self.get = self._queue.get
-
-
- def start(self):
-
- for i in range(self.min):
- self._threads.append(WorkerThread(self.server))
- for worker in self._threads:
- worker.start()
-
-
- def put(self, obj):
- self._queue.put(obj)
-
-
- def grow(self, amount):
- for i in range(amount):
- if self.max > 0 and len(self._threads) >= self.max:
- break
- worker = WorkerThread(self.server)
- self._threads.append(worker)
- worker.start()
-
-
- def shrink(self, amount):
-
- for t in self._threads:
- if not t.isAlive():
- self._threads.remove(t)
- amount -= 1
-
-
-
- if amount > 0:
- for i in range(min(amount, len(self._threads) - self.min)):
- self._queue.put(_SHUTDOWNREQUEST)
-
- class WorkerThread(threading.Thread):
-
- def __init__(self, server):
- self.ready = False
- self.server = server
-
- threading.Thread.__init__(self)
-
- def run(self):
-
- self.ready = True
- while True:
-
- conn = self.server.requests.get()
-
-
- if conn is _SHUTDOWNREQUEST:
- return
-
- self.conn = conn
-
- try:
-
- conn.communicate()
- finally:
- conn.close()
刚才咱们看到,WorkThread从消息队列中获取一个HTTPConnection对象,而后调用它的communicate方法,那这个communicate方法究竟作了些什么呢? apache
- class HTTPConnection(object):
-
- RequestHandlerClass = HTTPRequest
-
- def __init__(self, server, sock, makefile=CP_fileobject):
- self.server = server
- self.socket = sock
-
- self.rfile = makefile(sock, "rb", self.rbufsize)
- self.wfile = makefile(sock, "wb", self.wbufsize)
-
- def communicate(self):
-
- req = self.RequestHandlerClass(self.server, self)
-
- req.parse_request()
-
- req.respond()
在咱们具体看HTTPRequest.parse_request如何解析HTTP请求以前,咱们先了解下HTTP协议. HTTP协议是一个文本行的协议,它一般由如下部分组成: 编程
引用
请求行(请求方法 URI路径 HTTP协议版本)
请求头(譬如:User-Agent,Host等等)
空行
可选的数据实体
而HTTPRequest.parse_request方法就是把socket中的字节流,按照HTTP协议规范解析,而且从中提取信息(最终封装成一个env传递给webapp):
安全
- def parse_request(self):
- self.rfile = SizeCheckWrapper(self.conn.rfile,
- self.server.max_request_header_size)
-
- self.read_request_line()
-
- success = self.read_request_headers()
-
-
- def read_request_line(self):
-
- request_line = self.rfile.readline()
-
-
- method, uri, req_protocol = request_line.strip().split(" ", 2)
- self.uri = uri
- self.method = method
-
- scheme, authority, path = self.parse_request_uri(uri)
-
- qs = ''
- if '?' in path:
- path, qs = path.split('?', 1)
- self.path = path
-
-
- def read_request_headers(self):
-
- read_headers(self.rfile, self.inheaders)
-
-
- def read_headers(rfile, hdict=None):
- if hdict is None:
- hdict = {}
-
- while True:
- line = rfile.readline()
-
- k, v = line.split(":", 1)
-
- k = k.strip().title()
- v = v.strip()
- hname = k
-
-
- if k in comma_separated_headers:
- existing = hdict.get(hname)
- if existing:
- v = ", ".join((existing, v))
-
- hdict[hname] = v
-
- return hdict
至此咱们就分析完了HTTPRequest.parse_request方法如何解析HTTP请求,下面咱们就接着看看HTTPRequest.respond如何响应请求:
服务器
- def respond(self):
-
- self.server.gateway(self).respond()
在继续往下看代码以前,咱们先简单思考下,为何要有这个gateway,为何这里不把请求直接交给webapp处理?
我本身以为仍是出于分层和代码复用性考虑。由于可能存在,或者须要支持不少web规范,目前咱们使用的是wsgi规范,明天可能出来个ysgi,大后天可能还来个zsgi,若是按照当前的设计,咱们只须要替换HTTPServer的gateway属性,而不用修改其余代码(相似JAVA概念中的DAO层),下面咱们就来看看这个gateway的具体实现(回到本文最初,咱们在Server中注册的gateway是WSGIGateway_10):
WSGI网关 网络
- class WSGIGateway(Gateway):
- def __init__(self, req):
- self.req = req
- self.env = self.get_environ()
-
-
- def get_environ(self):
- raise NotImplemented
-
- def respond(self):
-
-
-
- response = self.req.server.wsgi_app(self.env, self.start_response)
-
-
- for chunk in response:
- self.write(chunk)
-
- def start_response(self, status, headers, exc_info = None):
- self.req.status = status
- self.req.outheaders.extend(headers)
-
- return self.write
-
- def write(self, chunk):
-
- self.req.send_headers()
-
- self.req.write(chunk)
WSGIGateway_10继承WSGIGateway类,并实现get_environ方法 app
- class WSGIGateway_10(WSGIGateway):
-
- def get_environ(self):
-
- req = self.req
- env = {
- 'ACTUAL_SERVER_PROTOCOL': req.server.protocol,
- 'PATH_INFO': req.path,
- 'QUERY_STRING': req.qs,
- 'REMOTE_ADDR': req.conn.remote_addr or '',
- 'REMOTE_PORT': str(req.conn.remote_port or ''),
- 'REQUEST_METHOD': req.method,
- 'REQUEST_URI': req.uri,
- 'SCRIPT_NAME': '',
- 'SERVER_NAME': req.server.server_name,
- 'SERVER_PROTOCOL': req.request_protocol,
- 'SERVER_SOFTWARE': req.server.software,
- 'wsgi.errors': sys.stderr,
- 'wsgi.input': req.rfile,
- 'wsgi.multiprocess': False,
- 'wsgi.multithread': True,
- 'wsgi.run_once': False,
- 'wsgi.url_scheme': req.scheme,
- 'wsgi.version': (1, 0),
- }
-
-
-
- for k, v in req.inheaders.iteritems():
- env["HTTP_" + k.upper().replace("-", "_")] = v
-
-
- return env