Re: [Twisted-Python] Unpersistable instead of pb.Avatar

2013-12-01 Thread Daniel Sank
>> It doesn't make sense to use the same perspective in >> both games >> > I don't see why not personally. I can think of two reasons. First, suppose that I would like to participate in two different games of chess at the same time. Suppose my Avatar class has a method for moving the chess pieces

Re: [Twisted-Python] Unpersistable instead of pb.Avatar

2013-12-01 Thread Flint
Hi, How do I fix this and actually send out new perspectives to users? > pb.Avatar is not a Referenceable object, the object which is sent when a client login is a wrapper againt the pb.Avatar object built like this: // pb.py L1327 if not IJellyable.providedBy(avatar): avatar = AsR

[Twisted-Python] Unpersistable instead of pb.Avatar

2013-11-29 Thread Daniel Sank
If I try to instance a pb.Avatar subclass and send it to a peer manually, the object that the peer receives is an Unpersistable instead of a real remote reference to the pb.Avatar. How do I fix this and actually send out new perspectives to users? Here's why I want to do this: Suppose I have a ne