Possibly only relevant to MCW_VOTE and my other feature enhancement suggestions (to be posted at the time of writing this - links to those related enhancements will be posted here).

Scenario

A KSP client side plugin needs to stop warp while another player has warp control or to prevent warp voting for a short period of time (and maybe a config option to set lock warp control for num seconds).

theoretical example

TAC life support mod detects that Jool Orbital station 1 is about to run out of oxygen (even though Bob Kerman is still 6 months away with the resupply, Charlie Kermans end of life is imminent).
If TAC decided to support DMP, it could hook into the DMP client and send 'HALT_WARP', 'Jool Orbital station 1 oxygen supply will run out soon'.
The server could then regain warp control and issue the following messages to all players:

If warp is already active, slow and stop warp:
"Warp has been halted - 'Jool Orbital station 1 oxygen supply will run out soon'"

If someone tries to gain warp:
"Warp is unavailable for num seconds - 'Jool Orbital station 1 oxygen supply will run out soon'"

This should give the players some time to address the situation, perhaps discuss or call for help in chat - and then finally continue warp voting.

I think this is going to have to go in a seperate mod that hooks into both DMP and TAC - And it's likely to require some co-ordination.

If TAC exposes a "there's something wrong" field, this will already be possible.

The secondary problem to this is the "Sync" button in subspace mode, perhaps we can disable the sync (or at least warn) for subspaces that would cause kerbal deaths.

If TAC exposes a "time left" field, this will also be possible, and most likely preferred.