The WebSocket protocol "Last Call"

As people here seem to really like and actively use WebSockets already, let me ask a question: How well does this behave with various proxy servers on both ends (client and server)?<p>I have this nagging feeling that yet another cool technology will probably not be usable for the foreseeable future because it gets broken in unpredictable ways by either forced proxy servers or, my bane of existence, personal firewalls.<p>Are there numbers out there about percentages of successful connections (though considering browser support, those numbers are probably skewed because this is still limited to early adopters which either don't run personal firewalls or are able to fix them)?<p>If connections fail, how do they fail?

Is there a good 'diff', detailing what's changed between revisions?<p>I need to read up on the latest version - anyone know if it avoids breaking http, and will work with proxies out of the box? (ie no essential body data without a content-length header)

Is there a good overview of websockets? I just glanced at the spec and it looks quite complex. Especially the part about framing. Do websockets have any relation to TCP sockets? If over TCP, why do they use their own framing?

Finally! I'm sick of web hosts claiming the protocol is still changing constantly, so they won't support websockets on their servers.