river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Re: Most trustworthy ServiceDiscoveryManager?
Date Thu, 16 Sep 2010 11:03:34 GMT
Peter Firmstone wrote:
> Well pepe's SDM is unmodified, I haven't managed to look at the latest 
> trunk yet, just got back from work, big day.
> In pepe, there is a concurrent dynamic policy, which you can switch 
> off or on as you like, when your not using the concurrent policy 
> provider, your using the original policy implementation.
> This may be useful for flushing out concurrency bugs in other code.
> To switch off the concurrent dynamic policy, after running ant 
> all.build, delete concurrent-policy-util.jar and your using the 
> original provider.
> Peter.
> Patricia Shanahan wrote:
>> I tried dropping my new TaskManager into a build based on Peter's 
>> pepe branch, and it is getting a couple of failures. The one that I'm 
>> analyzing appears to be related to some of the messier SDM code. That 
>> does not exclude the possibility that it is ultimately a TaskManager 
>> bug, but I would like to minimize the risk that it is an SDM bug.
>> There are currently two lines other lines of development, Peter's 
>> pepe branch, and Jonathan's attempts to get the trunk stable.

Actually the SDM has Bob's patch applied, Jonathan applied it to the 
main trunk also.
>> Which of those has the more solid SDM?
>> Thanks for any advice,
>> Patricia

View raw message