I have repurposed the Background thread class described by Peter here: https://v2archive.enroute.osgi.org/appnotes/concurrency.html, and added returning Promise to make it more usable.
I'm now looking for an implementation that provides the same confinement, but that can be scoped by users in the application (guess the qualifier could be just about anything really). Any great suggestion? I could surely have a cache per user that uses a Prototype version of the component and creates new Background threads and disposes of them once idle. Maybe something similar with a Thread pool. But I have the feeling that I'm missing something more clever and obvious. Cheers, Alain
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
