Todor Boev wrote:
Richard S. Hall wrote:
When a thread enters the POJO, it creates a copy of any services the
thread uses until the thread exits the POJO (even if the thread calls
out from the POJO and re-enters it). When the thread makes a request
for a service it always gets the same copy, so the thread never sees
a different value.
Of course, it is possible that its copy has departed and stopped
working, so it may throw exceptions, but that is the nature of OSGi
programming, so that is to be expected.
Couple of more questions :)
1) I have wondered for some time now why did you go with this
thread-local-like caching?
It was the only way that we could think of to make synchronization
transparent.
2) Is the caching implemented by the "requires" handler? I have some
plans to implement my flavor of service tracking handler where I
believe this caching will not be required.
Not sure, Clement will have to answer that.
-> richard
Todor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
