I changed it to highlite Nic's point that it's not feasible to resolve and provision osgi bundle transitive dependencies during deserialization because the time taken to do that can be excessive due to NP Complete nature of resolution.
It is incompatible with stream codebase annotations. I think Mic's currently arguing for a solution that relies on resolution and provisioning to occur during deserialization and I'm arguing against it. I'm arguing for a background task that preceeds deserialization of the proxy. Regards, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: Patricia Shanahan <p...@acm.org> Sent: 13/02/2017 11:27:27 pm To: dev@river.apache.org Subject: Re: OSGi NP Complete Was: OSGi - deserialization remote invocation strategy Sorry, I'm trying to find out the meaning of the current subject line. I'm not sure when it changed to "OSGi MP Complete". On 2/12/2017 10:50 PM, Michał Kłeczek wrote: > Sorry, NP Completness of what? > I have been the first to mention NP hardness of constraint satisfaction > problem > but I am not sure if this is what you are asking about. > > Thanks, > Michal > > Patricia Shanahan wrote: >> Are you literally claiming NP Completeness, or just using that as an >> analogy for really, really difficult? >> >
