HN user
Yes, I'm just referring to C10k because this demo uses a technique originally created to solve C10k.
Reaching 10 000 connections wasn't difficult in this case; it was just a matter of tuning a few system parameters. Exploring the APIs and studying how they can fit together was much more interesting, and sometimes challenging.
This system doesn't replace Django; it complements it.
You could build 95% of an application with the traditional request-response model and add the 5% of real-time featurs with a system similar to my demo.
(Of course, given your opinions on Django, I don't recommend you build anything with it.)
The C10k problem was originally about serving static files -- quoting the page you linked to: "take four kilobytes from the disk and send them to the network".
The demo could certainly be extended to send larger amounts of data -- left as an exercise for the reader.
I'm not sure to understand your second paragraph -- if I used this system in a real application, I would serve the pages with the traditional handler (with template rendering, middleware, etc.) and then exchange messages over the websocket. These are different roles.
Regarding database connections, the default behavior isn't the one you're describing any more; I implemented persistent connections in Django a few weeks ago.
Indeed, these are the exact reasons!
The porting strategy was decided by rough consensus in the core team.
We wanted a solution that would be convenient for authors of pluggable apps, so they could use the same strategy as Django itself. This is why we used six rather than an ad-hoc compatibility library.
Django targets Python >= 3.2, and Debian stable provides 3.1.
FYI the demo uses a manually compiled Python.
Since the showcase is low on information, here's a summary of the current status:
- the porting strategy is explained here: https://docs.djangoproject.com/en/dev/topics/python3/
- the porting work happens in the master branch; commits related to the Python 3 port are usually prefixed by [py3]: https://github.com/django/django/commits/master
- the test suite doesn't pass yet, but the hardest part is done: http://ci.djangoproject.com/job/Django%20Python3/
- most of the work happened over the last three weeks, and 5 or 6 core developers are contributing significantly
Obviously the Django ecosystem can't start supporting Python 3 until Django itself does.
The porting process (which is still in progress for Django) shouldn't be too difficult for most pluggable applications, as Django strongly encourages using unicode everywhere.
Polyconseil - Paris, France - Django developer
We are a small strategy consulting company focused on exploring new fields of activity. We have launched several spin-offs in the past years.
We are creating a large scale car sharing service (several thousand electric vehicles), launching in Q4. We are looking for highly productive and motivated developers to join our backend development team.
Interns with strong programming skills and learning abilities are welcome.
Drop me a line (aymeric.augustin@<company>.fr) or apply online at http://www.polyconseil.fr/careers/