C. Michael Pilato wrote: > Bert Huijben wrote: >> Shouldn't we handle this in the specific RA layers instead of globally for >> all ra-layers? >> >> That would allow removing the code for future code paths (like we did for >> HTTPv2), while this code would hide the issues if we ever reintroduce the >> bug? >> >> I'm pretty sure you fixed ra_local, so that is at least one ra layer that >> doesn't need this fix. > > So, I made this change with 1.6.x in mind. 1.6.x benefits universally from > this change because a) there's only codepath to debug if something is wrong, > b) 1.6.x code will never be able to optimize out the correction (because we > won't likely teach it to recognize newer servers), and c) I'm not proposing > the server fix for 1.6.x. > > But sure, I can move the corrective behavior into specific RA layers for > trunk.
r931581. -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
