On Tue, Jun 1, 2010 at 9:22 AM, Mike Hearn <span dir="ltr"><<a href="mailto:mike@plan99.net">mike@plan99.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">> HTTP-level solutions are vulnerable to broken proxies and caches, of which<br>
> there are many. This is why HTTP pipelining doesn't really work.<br>
<br>
</div>Yeah I know, but does that mean HTML should work around lack of<br>
features in HTTP? I mean you could say HTML5 is vulnerable to broken<br>
browsers :-)<br>
</blockquote></div><br>Yes, but if the browser has a bug it is much easier to detect, fix and deploy the fix.<br><br clear="all">Rob<br>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>