MASQ-Project
Shutdown command does not work as we thought
The supposed response on UiShutdownRequest, where UiShutdownResponse comes in mind, is never being sent actually. We miss this code in this request's handle in Neighborhood. It only exits the process of the Node which is quite brutal. At any rate, UishutdownResponse doesn't figure in the production code.
We will want to go even further with time going (to some last-bye communication with other Nodes before disconnecting) but for now we want to rectify that we don't send a full-valued response message to our UIs. They deserve more :)
Send a UiShutdownResponse from the same handle back to UiGateway. For that you may need to integrate subscribers of NodeToUiMessages in Neighborhood and this also requires a mortification of the BindMessage and of its handle. The following is just a temporal bridge but we also want to make sure that the response make it over to the UiGataway where it must be dispatched over the websocket connection, all in time, before the whole process terminates. So we probably want to sleep a while before we actually call exit_process().
