jensdietrich
commented
10 months ago Perhaps use observers / notifications + builder -- i.e. at top level (ProvenanceAgent) a builder or factory is referenced that can then create trackers. This builder/factory can be set by applications, or via service loaders etc. Trackers need APIs to support lifecycle, e.g. to avoid memory leaks. Trackers are information sinks, they make collected info available to clients, e.g. to serialise and attach to HTTP responses. Other implementations may include console logging, or trackers used for testing. We we would need to modify multiple trackers (as observers / listeners).
Matrixuniverses
At the moment all information is stored in trackers (singletons), this will need some abstraction to facilitate different contexts, for instance, attaching trackers to HTTP/JEE sessions or making then thread local or spring context etc.