-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> Stephan Richter wrote:
>> On Friday 17 November 2006 03:43, Chris Withers wrote:
>>> What do you suggest I do when the adapter needs to know the name it was
>>> registered for?
>> You can make the name part of the adapter API.
>
On Monday 27 November 2006 11:17, Benji York wrote:
> This seems somewhat analogous to a Python object being given multiple
> names. In that case too, there is no way for the object to know what
> it's names are.
Great analogy. I used that one before too, but did not think of it this time.
Regar
Chris Withers wrote:
I don't think it'll be a common pattern, but it doesn't feel right to me
that a named adapter (ie: one registered with a specific name) has no
way of finding out what name it has been registered with...
Because the same adapter can be registered more than once, it would
a
Stephan Richter wrote:
On Friday 17 November 2006 03:43, Chris Withers wrote:
What do you suggest I do when the adapter needs to know the name it was
registered for?
You can make the name part of the adapter API.
Not sure what you mean by this?
However, I would suggest revising the design;