Hello to all!
I see in the log file many failures like:
[Broker, client Failure: twisted.spread.pb.PBConnectionLost: [Failure
instance: Traceback (failure with no frames): < class
'twisted.internet.error.ConnectionDone'>: Connection was closed cleanly.]
All communications via PB use loopba
Laurens Van Houtven wrote:
> Are you familiar with interfaces? ITransport sounds like what you want.
Yes, and I implemented the ITransport methods.
The first bump was that I was missing registerProducer and
unregisterProducer, which are defined as part of IConsumer. But after
that I had another
On 04/08/2013 05:10 PM, Gerrat Rickert wrote:
>
> Some background:
>
> I have implemented a “relative frequency scheduler”.
>
> Tasks added to it are run with frequencies relative to one another –
> basically, if tasks 1-3 have relative frequencies of 1,2, and 3
> respectively, then task 2 is run
Some background:
I have implemented a "relative frequency scheduler".
Tasks added to it are run with frequencies relative to one another - basically,
if tasks 1-3 have relative frequencies of 1,2, and 3 respectively, then task 2
is run 1/2 as often as task 1, and task 3 is run 1/3 as often.
The
On Apr 8, 2013 9:44 PM, "Phil Budne" wrote:
> As a quick crock, I made my transport a subclass of
> twisted.internet.tcp.Server, and got away with it, but I'd like to do
> the right thing.
>
> I'd be delighted to find out that mixins exist that would solve my
> problem, but I'd be happy to know wh
I looked for, but haven't (yet) found any documentation on how
to implement a Twisted "transport"
For some testing and prototype work I'm doing I implemented the
proprietary TCP connection multiplexing protocol a customer of mine
uses as a Twisted Protocol and a transport for the "channels" that a
Hi Exarkun,
Thanks for coming back with this.
No problem if we exclude the spam filter tables. I don't need them.
Concerning the svn tables, if they don't carry additional information
linking revisions to other (trac-specific metadata), I don't need them
either.
I can understand your concerns r