| Namespace | Windows.Devices.Midi2.Transports.Rtp |
|---|---|
| Type Name | MidiRtpRemoteClientForgetConfig |
| Type | WinRT Runtime Class |
| Implements | IMidiServiceTransportPluginConfig |
| IDL | MidiRtpRemoteClientForgetConfig.idl |
Pass to MidiRtpTransportManager.ForgetRemoteClientAsync.
| Constructor | Description |
|---|---|
MidiRtpRemoteClientForgetConfig() |
Creates an empty configuration |
MidiRtpRemoteClientForgetConfig(hostId, remoteClientName) |
Creates a configuration with both values set |
| Property | Description |
|---|---|
HostId |
The GUID of the host on this PC |
RemoteClientName |
The name of the remote device, as the host’s decision has it |
Forgetting doesn’t turn anything away. A connection that’s already up keeps running. Only the decision is dropped, so the next time that remote device asks, it’s judged by the host’s RemoteClientPolicy alone.
This changes the running service right away. The saved allow and deny lists are separate, and you save them with MidiRtpHostKnownClientsConfig. An app that forgets a decision should do both, or the decision comes back the next time the service starts.
