Tornado VS Bottle

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.

Bottle.py: uber-fast and simple python web microframework, about 3x faster, saner, and more memory-efficient than Flask in my experience: https://github.com/bottlepy/bottle

Fossil: distributed version control and much more in a single executable, from the creators of SQLite: https://fossil-scm.org/

This walkthrough I am using as learning material says the vulnerable code (in the first snippet below, from github here: https://github.com/bottlepy/bottle/issues/900), is replicated in the webpage in the second snippet below and so I know this app is vulnerable to the exploit shown in highlighted in the github link.

Here's a web framework in a single file: bottle.py

I don't do much development for microcontrollers or limited resource environments, but it's nice to have a low boilerplate tool for throwing together quick web apps. I've used Bottle for that in the past. It looks like this might have more of an API focus, rather than templates or static pages? Very cool, will check it out.

However much makes sense for your project. bottle.py is a web framework in a single file, and it's about 4500 lines of code. Should you do the same thing? Probably not. But you can.

There was a time, I want to start a new project and have to choose what technologies to use for the frontend and backend parts as well. Research gets me to Aqueduct and Shelf, both of them weren't looking actively developing and supported and that leads me to the idea to make my own small micro-framework like Echo for Golang or Bottle for Python. And it was easy to decide: I've had time and motivation :)

It was developed by Marcel Hellkamp and Bottle was initially released on July 1 2009 it is cross-platform and open-source. its Github repository is https://github.com/bottlepy/bottle. It is integrated with Python, Vue JS, and Jinja.