Open Websockets were reasons for various bugs on battery drainage (bug 890154 for Facebook, bug 1003639 for ConnectA2, etc). There is no way for an app to listen for the device screen being switched off. Facebook fixed this by disconnecting the Websocket on visibilitychange. Doug Turner agreed in a thread about the FB issue that closing a websocket would be a good system behavior to prevent these bugs. Hopefully we can push this forward in thus bug.

What do we do for other network connections? I.e. what happens if we're half way through an XHR when the screen is turned off? Do we make the connection receive an error? If so I'm in favor of also cutting websocket connections.

which b2g release should this block harald? thx muchly!

Should we nom this for 2.2 so it doesn't fall off the radar?

Let's put this item in 2.2 for now. Before 2.2 starts, we can review these items with product management team to see which version we could put this item to. Do we know the possible effort on this? Thanks!

Use feature-b2g:2.2? rather than just 2.2.

richard, can you look at this post the ssl3 meltdown :/

How would ssl3 issues impact this bug?

My guess is that Doug was asking you to take a look when you had time.

Bug 1085760 will fix this, among other things, so I'm not seeing the need to keep a separate bug open here. Apparently I don't have the Bugzilla permissions to mark bug 1085760 "feature-b2g:2.2?". Could someone do that for me?