The idea is that when someone tries to execute a command that requires authorization, it is "added" to the Captain's queue. On the frontend, the captain can either accept or reject an action. If it is accepted, the captain's station will send the socket event and remove the action from the queue. If it is rejected, the captain will remove the action from the queue. Either way, the action is removed from the queue - the actual carrying out of the action is handled by the frontend and not the backend.
In addition, we haven't yet added any events to be authorized - I think we need to talk more about what needs to be authorized and what doesn't before we do this.
Hence submitting the pull request now and not later.
The idea is that when someone tries to execute a command that requires authorization, it is "added" to the Captain's queue. On the frontend, the captain can either accept or reject an action. If it is accepted, the captain's station will send the socket event and remove the action from the queue. If it is rejected, the captain will remove the action from the queue. Either way, the action is removed from the queue - the actual carrying out of the action is handled by the frontend and not the backend.
In addition, we haven't yet added any events to be authorized - I think we need to talk more about what needs to be authorized and what doesn't before we do this.
Hence submitting the pull request now and not later.