On Tue, Oct 21, 2008 at 5:41 PM, e. roman <[EMAIL PROTECTED]> wrote: > Rolled this back until a startup test perf regression is sorted out. > > http://code.google.com/p/chromium/issues/detail?id=3639
Ok, it is back in now as of r3776. > > On Tue, Oct 21, 2008 at 4:37 PM, e. roman <[EMAIL PROTECTED]> wrote: >> As of r3693, chrome.exe defaults to using the new http stack (rather >> than the WinHTTP stack). >> >> Please attach the label "NewHTTP" to bugs you encounter. >> Also describe whether it reproduces when using the --winhttp flag. >> >> Q: Why not continue using the WinHTTP implementation? >> A: Writing our own stack gives greater flexibility in fixing bugs, >> improving performance, and supporting other platforms. >> >> Kudos to Darin, Wan-Teh, Ricardo, and everyone else that worked on this. >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
