domonic VS Tornado

I did the 100th release of this python DOM 0.9.11... https://github.com/byteface/domonic

I've managed to tweak domonic (https://github.com/byteface/domonic) to work with elementpath (https://github.com/sissaschool/elementpath)...

I'm not sure about quicker. Doesn't scrapy use elementpath?. which converts a css query to an xpath under the hood as there is no complete CSSOM available for python. Likely as there is no modern standards based python dom to operate on so doing it on lxml tree is probably the best option. I find the main difference is xpath can return an attribute value where as css returns the node. You can use either from the terminal in my lib... https://github.com/byteface/domonic (as it uses elementpath like scrapy)

Thanks for your tool. I've been using it this week and updated a bunch of code. You are now a contributer... https://github.com/byteface/domonic/pull/58

[domonic](https://domonic.readthedocs.io/) will continue to evolve. It's a pure python dom I been working on in free time over last 2 years... https://github.com/byteface/domonic/

and used it on my lib yesterday... https://github.com/byteface/domonic/commit/96a91bbf3ee6f672bc1c0e5978f55e45706392aa

I am not expert in these but I thought Tornado's ioloop was readable enough for me to learn more event loops. Mostly, it was being implemented in pure Python.

https://github.com/tornadoweb/tornado/blob/branch4.5/tornado...

(Had to be in 4.5 because the newer versions 5.x and 6.x, it's switched to Python's stdlib asyncio)

I am a bit confused, Tornado is web server like a apache http server, or a framework like django, or both?

For Python, I use Tornado.

tornado? this https://github.com/tornadoweb/tornado ?

I'm writing a Node app that talks to a server that uses Tornado, a Python networking framework. The server uses WebSocket and structured JSON to expose RPCs, like sign_on called with the following message:

I've been using Python's Tornado (http://www.tornadoweb.org/) for years now.

Now on version 6, it's fast, well maintained, mature, and has good docs with readable code.

@bdarnell has done an excellent job maintaining it.

Here's one example:

Tornado supported async style co-routines before asyncio was a thing. Now it uses asyncio under the hood by default -- and it did so with an exceptionally smooth transition.

Tornado is another micro framework aimed at a specific use case: asynchronous networking applications. Tornado is well-suited for creating services that open a great many network connections and keep them alive that is, anything involving WebSockets or long polling. Moreover, It requires Python 3.5 or higher and drops Python 2 support entirely.

How to fix tornado.util.TimeoutError: Operation timed out after 5 seconds on tornado test debug?

Here's an official demo chat app using websocket: https://github.com/tornadoweb/tornado/tree/master/demos/websocket, though you should read the docs on websocket for understanding the code.