Partial impl for #57
FabricClient can register the service notification filter and unregister it.
See dotnet documentation
The registration mechanism is used inside the dotnet implementation of servicepartitionresolver
The registered service to get notification will no longer need to pass the previous endpoint resolve result to force a refresh. This is tested in the stateful example app. But the notification seems to be not very fast (lag of a couple of seconds). But this notification utilizes FabricClient cache, and reduces the cluster api load.
I will compare with direct resolution next.
Partial impl for #57 FabricClient can register the service notification filter and unregister it. See dotnet documentation The registration mechanism is used inside the dotnet implementation of servicepartitionresolver
The registered service to get notification will no longer need to pass the previous endpoint resolve result to force a refresh. This is tested in the stateful example app. But the notification seems to be not very fast (lag of a couple of seconds). But this notification utilizes FabricClient cache, and reduces the cluster api load. I will compare with direct resolution next.