You could always have some random-generated-at-startup "shutdown token" that you send through the WebSocket server itself, triggering it to break out of the loop.
On Mon, Sep 12, 2016 at 10:33 AM Sean McArthur <smcart...@mozilla.com> wrote: > > > > This may be a silly question, but why doesn't hyper come with > > WebSockets support out of the box? It seems like "part of" HTTP to > > some extent. > > > > Sorry this is offtopic from the subject, but just wanted to address the > question: > > You won't find websockets in hyper for the same reason you won't find it in > any other HTTP library: it's not part of HTTP. It's a separate spec, only > relevant to web browsers. > > It is always a goal though that hyper allows one to "upgrade" from HTTP/1.1 > to any other protocol, mostly by just giving up access to the underlying > socket. > _______________________________________________ > dev-servo mailing list > dev-servo@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo