As a followup, I have a candidate implementation of approach 1, based on the Mylyn 3.1 HEAD as of this morning, if that would help.
From: [email protected] [mailto:[email protected]] On Behalf Of Randall S. Becker Sent: March-01-09 1:15 AM To: [email protected] Subject: [mylyn-integrators] Inverted relationship to Monitor API request Hi All, I'm in a situation where I'd like to subscribe to Interaction Events in the Monitor API in addition to generating them. The situation is that I need a live feed of events in my organization for usage tracking - I'm trying to build something like a dashboard where I can see where people might need help due to excessive time spent in a task context. Can anyone provide guidance on this concept? Negative guidance is welcome too (as in: don't do it). >From an implementation standpoint, I can see two similar approaches, both having code introduced into InteractionEventLogger, where an independent plug-in could be notified each time interactionObserved is fired: 1. An addListener-style mechanism could allow any arbitrary class to subscribe using a GoF Observer pattern. 2. An extension point definition could be created allowing the InteractionEventLogger to use a factory instantiate the listeners and then perform the notify. Sincerely, Randall
_______________________________________________ mylyn-integrators mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
