Issue 5 in israfil-micro: Implement a strategy for re-registering a component for a given ID.

[codesite...@google.com]

Issue 5: Implement a strategy for re-registering a component for a
given ID.
http://code.google.com/p/israfil-micro/issues/detail?id=5

New issue report by christianedwardgruber:
There may be scenarios where the default strategy of "fail" is
unsuitable, for cases of attempting to
register a component with a key already in the container. Other
strategies may be "last one in
wins" or "first one in wins". Support for these alternate strategies
still needs to be maintained.

A key constraint on this is that no registration can happen after startup.

Issue attributes:
Status: Accepted
Owner: christianedwardgruber
Labels: Type-Enhancement Priority-Medium Milestone-Release-1.3
Component-Container Affects-all OpSys-All

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Issue 5: Implement a strategy for re-registering a component for a
given ID.
http://code.google.com/p/israfil-micro/issues/detail?id=5

Comment #1 by christianedwardgruber:
(No comment was entered for this change.)

Issue attribute updates:
Status: Investigating