Re: Clients 507 and 508 doing OGR-27 work

funny thing about this is that i just originated and carried on a thread in the 
perproxy list not more than 2 days before the start of OGR-27 and even then 
mentioned that OGR-27 would hopefully use a different project name than ogrng 
specifically to avoid this problem... what's wrong with naming the project after 
the actual project?

ie: ogr24, ogr24-2, ogr25, ogr26, ogr27, ogr28 etc (the -2 is the 
rework/validation project...



Jeff Lawson wrote:
> If you restart the personal proxy frequently, then this will tend to cause
> this bug to occur when the older clients manage to request OGR-NG work
> before your proxy has had a chance to talk to the upstream keyservers again.
> 
> The next proxy builds will probably fix this problem, but I would recommend
> that you avoid unnecessarily restarting the personal proxy (or just upgrade
> your old clients to versions that support OGR-27).
> 
> 
> 
>> This is some kind of bug in the proxy.
>>
>> All ogr-ng clients are capable of ogr-27, however prior to 509 they had a
>> bug that affects ogr-27 work and thus the results are useless.
>>
>>> I have a hunch, and it's only that, that v507 and v508 are capable of
>>> OGR-27
>>> after all.  Bovine's plan entry *may* have been more of an
>> "encouragement"
>>> to use v509 as there have been several OGR-related bug fixes in v509.
>>> Also,
>>> don't forget that v508 and up has a new OGR MMX core which is much, much
>>> faster than anything previous.


-- 
NOTE: NEW EMAIL ADDRESS!!

        _\/
       (@@)                      Waldo Kitty, Waldo's Place USA
__ooO_( )_Ooo_____________________ telnet://bbs.wpusa.dynip.com
_|_____|_____|_____|_____|_____|_____ http://www.wpusa.dynip.com
____|_____|_____|_____|_____|_____|____ ftp://ftp.wpusa.dynip.com
_|_Eat_SPAM_to_email_me!_YUM!__|_____ wkitty42 -at- windstream.net
_______________________________________________
rc5 mailing list
rc5-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected]
http://lists.distributed.net/mailman/listinfo/rc5