Allow graceful reloads in case of certificate changes

[jackie-t]

I currently can't find a way to gracefully reload websockify in case the certificate changes.

With graceful I'd mean something similar to haproxy - when you reload haproxy, all existing connections are still served, but new ones receive the new certificate. At the moment, I restart websockify, which terminates any connections.

This would - I imagine - become more needed with let's encrypt, especially if they intend to shorten the certificate validity further.

If this is already possible, documentation would help in avoiding similar questions. ;)

[CendioOssman]

Unfortunately I don't think it is likely we'll support this as it is not supported by multiprocessing, which is the core architecture of the current code. :/

[valerio-bozzolan]

Unfortunately I don't think it is likely we'll support this as it is not supported by multiprocessing, which is the core architecture of the current code. :/

Hello!

Apologies if I actually don't know well the codebase to understand if multiprocessing is something not related to this project. Does it exist an upstream bug about what you say?

Thank you.

[CendioOssman]

It's about the current architecture of websockify, so I don't think upstream Python needs to modify anything.