On Oct 1, 2013, at 1:13 AM, Laurens Van Houtven _...@lvh.io wrote:
On Tue, Oct 1, 2013 at 12:59 AM, Glyph gl...@twistedmatrix.com wrote:
Most of the code I can think of that wants to use that really wants the
transport rather than the protocol,
Yes, but having the protocol would also
On Tue, Oct 1, 2013 at 12:59 AM, Glyph gl...@twistedmatrix.com wrote:
Most of the code I can think of that wants to use that really wants the *
transport* rather than the protocol,
Yes, but having the protocol would also immediately give you access to the
transport, and, from what I
Hi everyone,
I think I've hit one of those cases where AMP really seems to want
everything (locator, receiver, sender) to be an instance of t.p.amp.AMP :-(
I've written some code that tries to multiplex stream transports over AMP:
On Sep 30, 2013, at 2:45 AM, Laurens Van Houtven _...@lvh.io wrote:
What am I doing wrong? Is this a bug?
I think it's pretty clearly a bug. Calling the argument proto in the first
place indicates the nature of the confusion.
There are parts of the flow here from bytes to method execution
On Sep 30, 2013, at 12:09 PM, Laurens Van Houtven _...@lvh.io wrote:
Hi Glyph,
Thanks for your response!
On Mon, Sep 30, 2013 at 8:41 PM, Glyph gl...@twistedmatrix.com wrote:
On Sep 30, 2013, at 2:45 AM, Laurens Van Houtven _...@lvh.io wrote:
What am I doing wrong? Is this a bug?
I
