I am plannig to upgrade twisted's buildbot in the near future. In
preperation for that, I am going to take down the production buildbot
on Tuesday, June 26, around 1600 UTC.
During that time, the result of any builds done will be lost. Thus, I'd
ask that people avoid committing to trunk during that time.
I will send a reminder before I take down the buildbot both here, and on
#twisted and #twisted-dev.
In case you missed it, we have now finally actually done something with twisted.org <http://twisted.org/> - thanks to Thomas Grainger, the top level of the domain is a Github Pages public site, which means you can contribute to it with fairly standard tools if you are so inclined! The repo is here: https://github.com/twisted/twisted.github.io <https://github.com/twisted/twisted.github.io>.
Trac will get migrated to new hardware somehow, volunteers are hard at work on that, but we should really move all the content that is hosted, for example, on the front page of twistedmatrix.com <http://twistedmatrix.com/> out of a trac wiki entirely, and into a more contributor-friendly space. This new domain is an opportunity to do that.
If you have a vision for what you'd like a clean, modern Twisted website to look like, well, you're only a PR away from achieving your dream. And if you just love website implementation but don't care about realizing your own vision (???), a literal straight port of the existing design into static HTML via some processor like Pelican so that others could contribute content would be much appreciated as well :-).
I need to push messages to clients stuck behind a firewall. Existing
solutions use polling of various forms. AMP would be perfect but for the
64k field size limit.
There has been a previous attempt to address this
(https://github.com/twisted/twisted/pull/1417) however this was reverted
with a request to split the PR into the type annotations (presumably
uncontroversial) and the protocol changes.
The original contributor has done the type annotations
(https://github.com/twisted/twisted/pull/1459) but they seem to be in
"review queue hell" Can someone take a look and either merge it or
specify what further work needs to be done?
With regard to the protocol changes there was discussion of using
netstrings. Is there any interest in a AMPv2 based on netstrings?
I ran across a PyCon APAC talk about this, and the speaker generously offered to write a blurb for our site, which I've posted here: https://twistedmatrix.com/trac/wiki/SuccessStories#BattlehouseGames <https://twistedmatrix.com/trac/wiki/SuccessStories#BattlehouseGames>
> Battlehouse creates and operates massively-multiplayer strategy games for browser and desktop platforms. Our most popular titles are nearly 10 years old and have served over 4 million users.
> Twisted plays an important role in our Python-based server stack. We use Twisted to handle many protocols including HTTP, WebSockets, and SQL. The asynchronous coroutine model helps us deliver low-latency gameplay without adding too much complexity to the codebase. Across 10 years of continuous evolution, Twisted has proven to be the most stable, well-documented, and flexible low-level networking library for Python.
> -- Dan Maas, CTO, Battlehouse Games
Do you have your own success story? Please contact success(a)twistedmatrix.com <mailto:firstname.lastname@example.org> - it's always nice to hear from users!