Boris Zbarsky wrote:
We have a server blacklist in necko and only enable pipelining after we get back the initial response and the server is not on that list. But the blacklist doesn't seem to be exhaustive. Or something.
Alas, presumably the blacklist isn't consulted if pipelining is disabled, as it is by default.
Seems we've a bit of a chicken and egg problem. We don't enable pipelining because of various problems, but we can't get traction on those problems without enabling pipelining.
Perhaps we should enable pipelining with a whitelist instead of a blacklist, so it only gets activated for servers we expect to be able to handle it reliably. Then we can more easily isolate the problems in our own implementation.
But we'd still need someone to be on top of those bugs, and maybe we don't have that person at the moment, in which case it wouldn't help us any to enable the feature.
-myk _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
