Am 14.01.2013 um 23:58 schrieb Glyph <gl...@twistedmatrix.com>:
>>> It seems like the "shared caching reference" would solve this problem
>>> as well?
>>
>> Yes, I think that's the right answer. It's certainly the right design
>> in my case, and perhaps in the general case too.
>
> I think that this is the right design for now, given the constraints of the
> current cred API; however, it's certainly possible we could think up an
> extension to the cred API that would make this case easier to deal with. It
> also leaves open some not-quite-trivial questions like "how do you know when
> to expire the cache, which are usually easy to work out for a particular
> application but do not generalize easily.
I was under the impression that the IRealm.requestAvatar() is *always* called
*once* after ICredentialsChecker.requestAvatarId() so I simply delete the data
from the cache once my avatar is created (and it works fine).
Am I presuming something I shouldn’t?
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
