Steve Holden wrote:
Write a class that implements a __call__() method, and use an instance
> of that class as your callback. Then the data can be stored as the
callback
> object's private instance data.
In fact, you needn't name the method __call__. You can pass in
Holder().method if you
atleta wrote:
> Hi,
>
> I'm working with a callback API (a DBus one) and I'd need to store
> some state between the calls somewhere. I know that it's possible to
> extend an object with fields after creation, so I could just store my
> data in the session object that is passed in with every call
atleta a écrit :
Hi,
I'm working with a callback API (a DBus one) and I'd need to store
some state between the calls somewhere. I know that it's possible to
extend an object with fields after creation, so I could just store my
data in the session object that is passed in with every callback.
H
atleta schrieb:
Hi,
I'm working with a callback API (a DBus one) and I'd need to store
some state between the calls somewhere. I know that it's possible to
extend an object with fields after creation, so I could just store my
data in the session object that is passed in with every callback.
Ho
On Fri, Jan 23, 2009 at 1:19 PM, atleta wrote:
> I'm working with a callback API (a DBus one) and I'd need to store
> some state between the calls somewhere. I know that it's possible to
> extend an object with fields after creation, so I could just store my
> data in the session object that is pa
Hi,
I'm working with a callback API (a DBus one) and I'd need to store
some state between the calls somewhere. I know that it's possible to
extend an object with fields after creation, so I could just store my
data in the session object that is passed in with every callback.
However it stinks fr
