Bug summary
__
Summary for 2010-10-10 through 2010-10-17
Opened Closed Total Change
Enhancements: 6 2668 +4
Defects: 4 0520 +4
Tasks: 0 0 7
On Oct 16, 2010, at 11:22 AM, Stefano Debenedetti wrote:
> Does this sound familiar in any way? Any suggestions off top of head
> while I try to come up with a self-contained sample which is
> reliably reproducing the issue I'm seeing happening only "sometimes
> and quite seldom[TM]"?
I can't re
On Oct 16, 2010, at 1:54 PM, disappearedng wrote:
> My trouble is I don't really know what to fill in in the else part of that
> second code part.
I don't understand what you're trying to achieve that your code isn't already
doing. Can you be more specific?
___
On Oct 16, 2010, at 10:02 AM, Marcus.CM wrote:
> How do i find out if a particular connection is already dead in the
> given "account" class?
There's no way to know; it's a race condition. If the connection dies before
authentication, then requestAvatar won't be called. If the connection die
Hello everyone, I am deploying twisted as a web server for my site. I am
looking into possibilities of reverse proxying.
I have the following code right now hooked up to my reactor for django. I am
using comet, and I realize that I absolutely must use port 80 hence I am
looking into possibilities
Apologies for the double posting, I am resending this because the
original message appears to have triggered some mbox format handling
bug somewhere and it appears truncated at the first content line
starting with "From" here:
http://twistedmatrix.com/pipermail/twisted-python/2010-October/023029.h
Hi,
I have a similar problem as described in this old mail [1] except
that I am not using threads at all.
Basically my app is a server that accepts connections from a client
(connection A), when A is established it opens connections B and C
to another server and forwards data from A to B and from
Hi,
This might seems like a trivial question or at least i would have
thought so but it has eluded me for some time on how to do this elegantly.
In twisted mail, since the only part where we instantiate an instance of
account is under :
def requestAvatar(self, avatarId, mind, *interfaces):
