When registering NotificationListeners with the NotificationConsumer, the registering capability only provides a reference to itself but no indication of which Topic it wants to subscribe to. It does a separate subscribe operation on the topic with the EPR of the resource.
However when a notification message is received, the notification consumer capability has to call accepts() method on each of the registered listeners. This seems like a performance issue if you have many capabilities and many notifications coming in. It would be better if the addMessageListener() also took a topic name. Or rather, a new method can be provided like setupSubscription() on the notification consumer that will also subscribe to the actual topic instead of the capability having to do this. if my understanding of the way this works is wrong, please excuse my ignorance and provide an explanation of the mechanism. also are there other cases in which subscriptions will have to be made by the capabilities only? Balan Subramanian Autonomic Computing, IBM, RTP, NC 919.543.0197 | [EMAIL PROTECTED]
