On 07:53 pm, wasi...@gmail.com wrote:
>Hello,
>
>I am implementing UDP-based protocol in Twisted (CoAP) which allows two
>behaviors when answering requests:
>
>1. If response is immediately available - send acknowledgement and
>response
>in a single datagram (piggyback response)
>2. If response ne
Hello,
I am implementing UDP-based protocol in Twisted (CoAP) which allows two
behaviors when answering requests:
1. If response is immediately available - send acknowledgement and response
in a single datagram (piggyback response)
2. If response needs to be fetched or prepared - send datagram wi
> >Any hint how to track that down would be great!
>
> The `protocol´ attribute isn't part of the transport interface. Some
> transports
> are implemented in a way such that changing that attribute to refer to a
> different protocol will produce the behavior you're after, but not all. In
> part
On 01:19 pm, tobias.oberst...@tavendo.de wrote:
>Hello,
>
>I am running a Twisted Web Site object that switches the protocol for
>specific paths.
>The goal is to run Twisted Web, and have certain paths mapped to
>WebSocket.
>
>I am aware of
>
>http://twistedmatrix.com/trac/ticket/3204
>
>but in t
Hello,
I am running a Twisted Web Site object that switches the protocol for specific
paths.
The goal is to run Twisted Web, and have certain paths mapped to WebSocket.
I am aware of
http://twistedmatrix.com/trac/ticket/3204
but in the meantime have working code
https://github.com/tavendo/Au
