Community
Participate
Working Groups
I keep making the mistake of forgetting to call DsfSession.addServiceEventListener() when adding a @DsfServiceEventHandler to a class for the first time. I always found this DSF requirement annoying. After talking with Francois who also uses the @ServiceEventHandler pattern in the tracing framework (TMF), he suggested to automatically call DsfSession.addServiceEventListener() in AbstractDsfService.register() if any @DsfServiceEventHandler is present. And similarly to call removeServiceEventListener() from unregister(). This would allow extenders of DSF to simply use @DsfServiceEventHandler without needed to remember to add the class as an eventListener. We didn't look at the details of it, or done any prototype, but it seemed like a good idea. I believe we could do this without any API changes or breaking existing behavior, so we could even do it for Indigo, although not necessary.
+1 Makes sense to me.