CodeIgniter VS Tornado

CodeIgniter is an open-source PHP framework with 18k+ stars and 7.8K forks on GitHub. It follows the Model-View-Controller (MVC) architecture and provides a structured way to create and organize code. It provides a set of libraries and an intuitive interface to accelerate PHP web app development.

Over the years I have tried different frameworks, mostly in PHP, like Code Igniter (2010), ProcessWire (2014) and Laravel (2015).

CodeIgniter is an open-source php web application framework created by EllisLab Inc and it is now a project of British Columbia Institute of Technology. The framework implements a modified version of the Model-View-Controller design pattern. It is praised for its performance and the quality of its documentation. It's currently licensed under the MIT License, although the previous version was released under the Open Software License ("OSL") v. 3.0.

Look at the issues and pull requests. It doesn’t support php 8 properly, hence why I call it outdated https://github.com/bcit-ci/CodeIgniter/issues

CodeIgniter

It's been a long time since I wrote any PHP in anger but back when I did, I got a ton of mileage out of CodeIgniter (https://codeigniter.com/). It looks like it's still around and being actively maintained. I can quite clearly remember a number of projects that went from being just an idea to 90% functional in the span of an evening.

I write Python almost exclusively now, but still pine for something like CodeIgniter. Flask is nice because it lets you bolt on whatever you want, but you spend a lot of time choosing, prototyping, and often discarding libraries. Django does a lot of heavy lifting but has (IMO) a very steep learning curve. There doesn't seem to be anything (or at least anything I've liked) in between.

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.