You need to be logged in to post in the forums. If you do not have an account, please sign up first.
Pipelining - how does Opera decide to avoid it?Hi,
I am developing a middleware that doesn't handle pipelining well. Additionally, I perform my own acceleration so that pipelining actually doesn't help.
When Opera browser is connected to my system, the results are corrupt web page.
I would like to be able to "persuade" Opera to refrain from pipelining, with as little as possible deterioration of the performance. I saw in various forums that Opera applies heuristics to make the pipelining yes/no decision, and I know that at least in the past IIS did not support pipelining and Opera somehow detected this and did not apply pipelining.
Can anyone tell me what these heuristics are? The best I came with was to simply ignore the pipeline requests which would require the browser to reattempt the GET message, but I assume this will slow the operation down since in the absence of socket tear down, the browser will have to make a decision based on timeout to the response.