This is apparently so important that we never opened an issue for it. (Did we? We have discussed it incessantly but I can't find it.)
The idea is to allow sessions to continue running when the web page goes away. It probably requires another pane to show your running sessions so you can manually disconnect, but also returning to the same notebook should by default reconnect.
This solves at least three problems:
intermittent connection problems / networks that are hostile to web sockets
allowing long-running notebooks to do their thing, and returning to the results later.
gordonwoodhull
commented
9 years ago
This is apparently so important that we never opened an issue for it. (Did we? We have discussed it incessantly but I can't find it.)
The idea is to allow sessions to continue running when the web page goes away. It probably requires another pane to show your running sessions so you can manually disconnect, but also returning to the same notebook should by default reconnect.
This solves at least three problems:
It also will help with #339 notebook scheduling.
It's definitely not easy, because it requires buffering results on the server.
We have to figure out how to do this without just leaving everything running.