04.08.2009, в 16:47, Ian Hickson написал(а):

The text "Closing the connection causes a close event to be fired and the
readyState attribute's value to change, as described below" is not
normative (it has no "must"s in it). It's just letting you know that
subsequent requirements as described lower in the spec do result in that.

Is there some way I can make that clearer?


A note explaining that the close event will be dispatched at server's discretion (or on subsequent connection timeout), potentially long time after close() is called, would likely make the intention clearer.

- WBR, Alexey Proskuryakov

Reply via email to