To enable arbitrarily long websocket connections, we set readtimeout = 0 on HTTP.listen. The downside of this is that also standard HTTP requests are kept open. When running with verbose=true, one gets several Closed (x): ... Info's per viewer of index.html some minutes after having stopped the server. It's always the ones not corresponding to a websocket.
This is invisible in non-verbose mode, and does not bind many resources, so it is not severe. But it should be addressed anyway, which needed to be done in HTTP.jl. So we'd have to think about a good way of doing this (having a websocket-specific readtimeout with default 0) and file another pull request...
To enable arbitrarily long websocket connections, we set
readtimeout = 0onHTTP.listen. The downside of this is that also standard HTTP requests are kept open. When running withverbose=true, one gets severalClosed (x): ...Info's per viewer ofindex.htmlsome minutes after having stopped the server. It's always the ones not corresponding to a websocket.This is invisible in non-verbose mode, and does not bind many resources, so it is not severe. But it should be addressed anyway, which needed to be done in
HTTP.jl. So we'd have to think about a good way of doing this (having a websocket-specificreadtimeoutwith default 0) and file another pull request...