[Twisted-Python] Supporting a two-part client protocol.
Go Luhng
goluhng at gmail.com
Mon Feb 3 17:18:26 MST 2020
> Colin Dunklau wrote:
>
> Assuming the header has a fixed length,
It does. The header is just a serialized C struct, so it's
fully-specified for length and offset of each field.
> OTOH, that's for stream protocols, so if you want to eventually handle
> UDP, it's probably nicer to do the full sans-io thing
> (https://sans-io.readthedocs.io/) and wire it up with a more-basic
> Twisted protocol.
Could you elaborate on this? I'm new to Twisted, and also unfamiliar
with sans-io.
Specifically, I'm wondering what type of "more-basic" Twisted protocol you mean.
More information about the Twisted-Python
mailing list