Maybe I misunderstand the issue, but I believe the Endpoints API solves for this. https://twistedmatrix.com/documents/16.4.1/core/howto/endpoints.html
This abstracts the transport and allows you to focus on only interpreting the bytes transmitted over that transport by defining a Protocol and a Factory that plug into strports. This should allow you to have the business logic defined in only one location while listening/requesting over different transports. On Wed, Aug 16, 2017, 07:15 Tristan Seligmann <mithra...@mithrandi.net> wrote: > On Wed, 16 Aug 2017 at 13:53 Jarosław Fedewicz < > jaroslaw.fedew...@gmail.com> wrote: > >> One thing that is also notably missing from the puzzle is that there is >> no support for datagram endpoints. >> > > The lack of datagram endpoint abstractions is definitely just a "we > haven't gotten around to it yet"; stream endpoints were the initial focus > mainly because stream protocols are a lot more common than datagram > protocols. The ticket covering datagram endpoints is here, I believe: > https://twistedmatrix.com/trac/ticket/4471 There seems to be some old > work that was never completed, so picking this up again might be a good > starting point if you're keen on contributing in this area. > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python >
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
