…l(), except it looks for a specific delimiter. This function is used to parse the header of the website, where it is delimited by '\n' only (like http://news.ycombinator.com/rss)
…ementation. There don't seem to be any differences on the server side.
All protocol-specific functions are moved to the former WebSocketRequest class, which is renamed to WebSocketProtocol76. The WebSocketHandler chooses the right WebSocketProtocol implementation by looking at the request headers.
PUT requests have bodies
tornado.netutil.bind_unix_socket can create non-blocking listening unix sockets, and HTTPServer can use them. (no client-side support for this yet) This is useful e.g. with nginx proxying incoming TCP traffic to a backend over a unix socket (which may be easier to manage than a set of TCP ports)
This is a significant speedup for small requests, since it is now possible to do a request and (synchronous) response without calling IOLoop.add_handler.
…ite. This speeds things up a bit by avoiding a system call to add a handler for errors that is just replaced by the first read or write.