Niclas Hedhman wrote:
You realize that this is a very expensive procedure? Not sure exactly when you
mean the above should take place, but it sounds like "very often"...
IMHO, the only reasonable approach is to share the handlers within the JVM
(i.e. solution 2). Better yet if the sharing mechanism could be used (or
cooperating with) the world "outside" OSGi.
That was my main concern, but I don't have any hard numbers to back it up.
I don't know that this would happen "very often", it would happen when
someone tried to open a URL that wasn't handled by a built-in handler,
correct? I am not sure how often that would be.
I am not against #2, however, the most logical to me seems to be #3
since otherwise you are bleeding services among framework instances. Are
there other ways of doing #3?
-> richard
