On Monday 21 September 2009 23:35:54 Evan Daniel wrote:
> Builds 1234-1236 included several changes to routing that we hope
> improved things. Specifically:
> - The "loop fix": when node A is choosing how to route a request it
> received from node B, when considering node C's FOAF locations, it
>
On Thu, Sep 24, 2009 at 11:23 AM, Matthew Toseland
wrote:
> On Monday 21 September 2009 23:35:54 Evan Daniel wrote:
>> Builds 1234-1236 included several changes to routing that we hope
>> improved things. ?Specifically:
>> - The "loop fix": when node A is choosing how to route a request it
>> rece
On Thu, Sep 24, 2009 at 11:23 AM, Matthew Toseland
wrote:
> On Monday 21 September 2009 23:35:54 Evan Daniel wrote:
>> Builds 1234-1236 included several changes to routing that we hope
>> improved things. ?Specifically:
>> - The "loop fix": when node A is choosing how to route a request it
>> rece
On Thu, Sep 24, 2009 at 11:23 AM, Matthew Toseland
wrote:
> On Monday 21 September 2009 23:35:54 Evan Daniel wrote:
>> Builds 1234-1236 included several changes to routing that we hope
>> improved things. Specifically:
>> - The "loop fix": when node A is choosing how to route a request it
>> rece
On Thu, Sep 24, 2009 at 11:23 AM, Matthew Toseland
wrote:
> On Monday 21 September 2009 23:35:54 Evan Daniel wrote:
>> Builds 1234-1236 included several changes to routing that we hope
>> improved things. Specifically:
>> - The "loop fix": when node A is choosing how to route a request it
>> rece
On Monday 21 September 2009 23:35:54 Evan Daniel wrote:
> Builds 1234-1236 included several changes to routing that we hope
> improved things. Specifically:
> - The "loop fix": when node A is choosing how to route a request it
> received from node B, when considering node C's FOAF locations, it
>
Builds 1234-1236 included several changes to routing that we hope
improved things. Specifically:
- The "loop fix": when node A is choosing how to route a request it
received from node B, when considering node C's FOAF locations, it
should ignore locations among C's peers that exactly match B's
loc
Builds 1234-1236 included several changes to routing that we hope
improved things. Specifically:
- The "loop fix": when node A is choosing how to route a request it
received from node B, when considering node C's FOAF locations, it
should ignore locations among C's peers that exactly match B's
loc
