tl;dr Does Whimsy Agenda Tool keep sockets open to the server after displaying the page?
I finally started using Chrome and after opening several tabs with agenda pages, I opened another and got this message about “Waiting for available socket…” So I looked on the internet and found this: http://stackoverflow.com/questions/23679968/chrome-hangs-after-certain-amount-of-data-transfered-waiting-for-available-soc It looks like Chrome only allows six connections to the same server simultaneously. So my question is: Why does whimsy agenda keep sockets open to the whimsy server after displaying the page? That would explain a number of issues that I’ve been having. Perhaps Safari has a similar limit but doesn’t tell you about it. “Here are the maximum number of HTTP connections which you can make with a Chrome browser: • The maximum number of connections per proxy is 32 connections. This can be changed in Policy List. • Maximum per Host: 6 connections. This is likely hardcoded in the source code of the web browser, so you can't change it. • Total 256 HTTP connections pooled per browser. Source: Enterprise networking for Chrome devices ( https://support.google.com/chrome/a/answer/3339263?hl=en )” I verified that I did have six tabs open to the agenda (various tabs) and when I closed one of them, the seventh tab became responsive again. Craig L Russell Secretary, Apache Software Foundation [email protected] http://db.apache.org/jdo
