Tornado 1.2

Switched from Django to Tornado a few month ago, and I've never looked back since. In Tornado everything just seems to makes sense and nothing gets in your way. I've worked with Django for couple years and never felt this way.

There's also Cyclone which I've used with great success for some intranet sites. Like it very much and definitely worth checking out IMHO:<p>Cyclone is a low-level network toolkit, which provides support for HTTP 1.1 in an API very similar to the one implemented by the Tornado web server - which was developed by FriendFeed and later released as open source / free software by Facebook.<p>Key differences between Cyclone and Tornado<p><pre><code> * Cyclone is based on Twisted, hence it may be used as a webservice protocol for interconnection with any other protocol implemented in Twisted. * Localization is based upon the standard Gettext instead of the CSV implementation in the original Tornado. Moreover, it supports pluralization exactly like Tornado does. * It ships with an asynchronous HTTP client based on TwistedWeb, however, it's fully compatible with one provided by Tornado - which is based on PyCurl. (The HTTP server code is NOT based on TwistedWeb, for several reasons) * Native support for XMLRPC and JsonRPC. (see the rpc demo) * WebSocket protocol class is just like any other Twisted Protocol (i.e.: LineReceiver; see the websocket demo) * Support for sending e-mail based on Twisted Mail, with authentication and TLS, plus an easy way to create plain text or HTML messages, and attachments. (see the e-mail demo) * Built-in support for Redis, based on txredisapi. We usually need an in-memory caching server like memcache for web applications. However, we prefer redis over memcache because it supports more operations like pubsub, various data types like sets, hashes (python dict), and persistent storage. See the redis demo for details. * Support for HTTP Authentication. See the authentication demo for details. </code></pre> Advantages of being a Twisted Protocol<p><pre><code> * Easy deployment of applications, using twistd. * RDBM support via: twisted.enterprise.adbapi. * NoSQL support for MongoDB (TxMongo) and Redis (TxRedisAPI). * May combine many more functionality within the webserver: sending emails, communicating with message brokers, etc... </code></pre> <a href="https://github.com/fiorix/cyclone" rel="nofollow">https://github.com/fiorix/cyclone</a>

So is anyone big using Tornado in production? I expected the development to stall with the buyout of Friendfeed

Whats the difference between tornado and node.js? Besides the obvious that they are developed in different languages.

I see references to fixing problems on Windows, but there's no mention of Windows support or installation, nor does the hello-world example run (I get the same failed import on the fcntl module that I always have, even after upgrading).<p>Does it run under Cygwin?

Is the main advantage of Tornado that when you have a site open in the browser, it is less expensive for the site to push updates to the browser?

I don't know how programmers can convince themselves that a framework based on callbacks (event driven) is a good idea.

I'm using it to power <a href="http://www.locacha.com" rel="nofollow">http://www.locacha.com</a> still in beta.