OK great. I have currently implemented this for our product down stream in some Go code. Do you have any direction on where you would like this upstream?

Well first implement the dynamic channel, and then probably touch the functions that handle mouse moves and keyboard strokes to either use the old path or the new dynamic channel...

@pookaboydunc but a full go runtime might be a little overkill for such a feature ;)
(the channel only tunnels the existing mouse/keyboard events over a dynamic channel to make it more conform with UDP transport - which we currently also not implement)

but a new channel (similar to our own try of that with ainput) would be really appreciated.
should most likely just check for existence and then send over that transport in rdpInput::MouseEvent et al function pointer implementations.

input_register_client_callbacks is the place all of them are set up.
currently only hard coded fastpath and slowpath implementations, but this could be extended to check for an existing (and initialized) dynamic channel and use that if an event is sent.

Thanks for the advice @akallabeth. I have been given the go ahead from work to crack on with this so all going well i should get something in. I will reach out if I need any more advice etc.