Connecting your software - and having fun too!
Basic network servers with Twisted.
And basic clients.
Code without tests is broken by definition; Twisted makes it easy to test your network code.
- The Evolution of Finger: building a simple finger service
- The Evolution of Finger: adding features to the finger service
- The Evolution of Finger: cleaning up the finger code
- The Evolution of Finger: moving to a component based architecture
- The Evolution of Finger: pluggable backends
- The Evolution of Finger: a clean web frontend
- The Evolution of Finger: Twisted client support using Perspective Broker
- The Evolution of Finger: using a single factory for multiple protocols
- The Evolution of Finger: a Twisted finger client
- The Evolution of Finger: making a finger library
- The Evolution of Finger: configuration and packaging of the finger service
Networking and Other Event Sources
A brief overview of the
The event loop at the core of your program.
Add some security to your network transport.
How to use Twisted’s UDP implementation, including multicast and broadcast functionality.
Launching sub-processes, the correct way.
Like callback functions, only a lot better.
In-depth information on Deferreds.
More about Deferreds.
Timeouts, repeated events, and more: when you want things to happen later.
Running code in threads, and interacting with Twisted in a thread-safe manner.
How to pause when buffers fill up.
GTK+, Windows, epoll() and more: use your GUI of choice, or a faster event loop.
Create configurable applications that support multiple transports (e.g. TCP and SSL).
When inheritance isn’t enough.
Implementing authentication and authorization that is configurable, pluggable and re-usable.
A generic plugin system for extendable programs.
Deploying Twisted Applications
twistdlets you daemonize and run your application.
Writing code that
systemdto launch and monitor Twisted applications.
Keep a record of what your application is up to.
Using SQL with your relational database via DB-API adapters.
The command-line argument parsing used by
A simplistic way to store data on your filesystem.
More information on writing tests.
Using wrappers for sendmsg(2) and recvmsg(2).
Asynchronous Messaging Protocol (AMP)
A two-way asynchronous message passing protocol, for when HTTP isn’t good enough.