15210 2011-12-15 13:20:42 +0000 Consider dispatching an event when bufferedAmount drops to 0 2012-12-31 04:59:29 +0000 1 1 1 Unclassified WebAppsWG WebSocket API (editor: Ian Hickson) unspecified Other other RESOLVED REMIND v2; might mark this LATER after checking on implementation status — this should be amongst the next batch of additions to the API ,though P3 enhancement --- 15209 1 bugs ian art.barstow brian.raymor ian jduell.mcbugs mike public-webapps public-webapps-bugzilla oldest_to_newest 61599 0 bugs 2011-12-15 13:20:42 +0000 Right now the spec has example socket.onopen = function () { setInterval(function() { if (socket.bufferedAmount == 0) socket.send(getUpdateData()); }, 50); }; That works, sure, but in many cases there shouldn't be a need for such interval. Especially in worker context something like: socket.onemptybuffer = function () { socket.send(getUpdateData()); }; could work quite nicely. 63256 1 ian 2012-01-28 22:13:34 +0000 Yeah, that's probably reasonable. I expect we'll add this in due course. Probably best to let the implementations catch up with the protocol changes and deploy more widely before adding more stuff, though. 71360 2 ian 2012-07-24 06:00:27 +0000 This should probably be done at the same time as bug 15209. 80753 3 ian 2012-12-31 04:59:29 +0000 Marking this and bug 15209 as REMIND for now. Will reopen in a few months and see whether we've found that it's a real problem or not.