In proxy injection mode, we need to increase the browser's max open connections, which usually defaults to 2 or 4. (Otherwise, the long-lived poll to the server asking for work may lock up the app, especially if we also turn on browser side logging, which creates even more HTTP requests.)

In IE/Windows, you can increase the maximum number of open connections by setting the "MaxConnectionsPerServer" registry key. This doesn't appear to affect the max open connections for Safari/Windows. That's puzzling to me, because as far as I can see, Safari/Windows is just using the standard WinInet function HttpOpenRequest (they use the ASCII version HttpOpenRequestA), which is morally supposed to honor that limit. (Perhaps I'm not testing this correctly?) http://svn.webkit.org/repository/webkit/trunk/WebCore/platform/network/win/ResourceHandleWin.cpp