Re: Extra Connection Support Proposal

We are still faced with the fundamental problem that if a browser that 
observes the two connection limit and two long-lived connections are 
currently open and the user does something that triggers another request 
(such as opening another tab), the browser is stuck and essentially hangs 
waiting for a connection to become available. This is a serious usability 
issue. Is there something that I need to do to improve my proposal, so can 
effectively tackle this issue, and provide a means for authors to inform the 
user agents when a response is long-lived?
Thanks,
Kris