HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
fiorix
cyclone
Python2010–2011
fiorix / cyclone

cyclone

Cyclone is a web server framework for Python, that implements the Tornado API as a Twisted protocol.

Web DevelopmentSystems & Infrastructure
Explore on GitHubRead Hacker News discussions
3Distinct people
6Mentions
0Explicit recommenders
691GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Cyclone is a web server framework for Python, that implements the Tornado API as a Twisted protocol.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month6 dated mentions

Observed mentions: 2010-03-24 23:03:50 UTC to 2011-08-31 04:08:10 UTC.

012010-03-01 00:00:00 UTC to 2010-04-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 20102010-04-01 00:00:00 UTC to 2010-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-05-01 00:00:00 UTC to 2010-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-06-01 00:00:00 UTC to 2010-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-07-01 00:00:00 UTC to 2010-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-08-01 00:00:00 UTC to 2010-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-09-01 00:00:00 UTC to 2010-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2010-10-01 00:00:00 UTC to 2010-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2010-11-01 00:00:00 UTC to 2010-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 20102010-12-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-01-01 00:00:00 UTC to 2011-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-02-01 00:00:00 UTC to 2011-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-03-01 00:00:00 UTC to 2011-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-04-01 00:00:00 UTC to 2011-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-05-01 00:00:00 UTC to 2011-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-06-01 00:00:00 UTC to 2011-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-07-01 00:00:00 UTC to 2011-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-08-01 00:00:00 UTC to 2011-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 2011

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 20102010-03-01 00:00:00 UTC2010-04-01 00:00:00 UTC110
Apr 20102010-04-01 00:00:00 UTC2010-05-01 00:00:00 UTC000
May 20102010-05-01 00:00:00 UTC2010-06-01 00:00:00 UTC000
Jun 20102010-06-01 00:00:00 UTC2010-07-01 00:00:00 UTC000
Jul 20102010-07-01 00:00:00 UTC2010-08-01 00:00:00 UTC000
Aug 20102010-08-01 00:00:00 UTC2010-09-01 00:00:00 UTC000
Sep 20102010-09-01 00:00:00 UTC2010-10-01 00:00:00 UTC101
Oct 20102010-10-01 00:00:00 UTC2010-11-01 00:00:00 UTC000
Nov 20102010-11-01 00:00:00 UTC2010-12-01 00:00:00 UTC000
Dec 20102010-12-01 00:00:00 UTC2011-01-01 00:00:00 UTC101
Jan 20112011-01-01 00:00:00 UTC2011-02-01 00:00:00 UTC000
Feb 20112011-02-01 00:00:00 UTC2011-03-01 00:00:00 UTC101
Mar 20112011-03-01 00:00:00 UTC2011-04-01 00:00:00 UTC000
Apr 20112011-04-01 00:00:00 UTC2011-05-01 00:00:00 UTC000
May 20112011-05-01 00:00:00 UTC2011-06-01 00:00:00 UTC000
Jun 20112011-06-01 00:00:00 UTC2011-07-01 00:00:00 UTC101
Jul 20112011-07-01 00:00:00 UTC2011-08-01 00:00:00 UTC000
Aug 20112011-08-01 00:00:00 UTC2011-09-01 00:00:00 UTC101

What Hacker News says

6 sources
wil2k·Feb 21, 2011
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: 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. Key differences between Cyclone and Tornado * 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 compat
Read the rest
ible 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. Advantages of being a Twisted Protocol * 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... https://github.com/fiorix/cyclone
In Tornado 1.2

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.