[Twisted-Python] Re: Disabling PB (de)serialization

[Steve Freitas]

On Fri, 2005-09-02 at 07:10 +0200, Stefano Masini wrote:
> if you don't want to go as low level as to rewrite a custom serialization
> protocol for pb, why don't you use two channels, like in good old ftp?
> One for control, and the other for data?

That's what I did for my application -- I had a similar need, so I set
up another protocol to listen on another port, use the control channel
(PB) to coordinate the connections, generate random tokens to provide
some means of verifying that the connecting client is who I think it is,
and so on. It works quite well, but it certainly would be sweet if PB
had the ability to, say, declare certain methods to send and receive raw
data only.

Steve