river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter <j...@zeus.net.au>
Subject Re: OSGi NP Complete Was: OSGi - deserialization remote invocation strategy
Date Mon, 13 Feb 2017 07:34:54 GMT
Also see the OSGi Enterprise specification, v6, Chapter 136, page 691, 
there's some discussion about the NP-complete nature of dependency 
resolution there as well.

https://www.osgi.org/developer/downloads/release-6/release-6-download/

On 13/02/2017 5:19 PM, Peter wrote:
> OSGi Dependency resolution is.
>
> http://underlap.blogspot.com.au/2010/02/osgi-resolution-is-np-complete-so-what.html 
>
>
> Which means if we want to support an OSGi environment properly, we may 
> need some time to resolve the dependencies for a smart proxy, before 
> deserializing the proxy, rather than downloading the proxy dynamically 
> during unmarshalling, it's better to delay unmarshalling until the 
> dependencies are resolved, so the client isn't impacted by delays.
>
> Cheers,
>
> Peter.
>
> On 13/02/2017 4: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?
>>>
>>
>>
>
>


Mime
View raw message