The existing discovery mechanism where the services reside in a plugin-managed observable collection is geared towards displaying services in a UI and having the user select one. In other use cases the client might want to maintain the collection manually (for example if the results must be filtered) or just react to the found / lost events without maintaining a collection at all. This should be trivial to add and will give the user more choice.
Scenario
Use the plugin in my own application via Flutter dependency
Description
The existing discovery mechanism where the services reside in a plugin-managed observable collection is geared towards displaying services in a UI and having the user select one. In other use cases the client might want to maintain the collection manually (for example if the results must be filtered) or just react to the found / lost events without maintaining a collection at all. This should be trivial to add and will give the user more choice.
Scenario
Use the plugin in my own application via Flutter dependency
Platform
All of them