…tion to get the ids and build a map of our own, rather than relying on the ServiceRemotingDispatcher. The reason is that
it's quite difficult to access the map for the actor. This approach is almost much cleaner, with less reflection calls. Both actor and services on both client and handler sides have switched to use the new MethodNameProvider, which implements this new approach.
Removed the base class CorrelatingProxyFactory as it seemed unnecessary after factoring out the method name provider into a separate class.
…tion to get the ids and build a map of our own, rather than relying on the ServiceRemotingDispatcher. The reason is that
it's quite difficult to access the map for the actor. This approach is almost much cleaner, with less reflection calls. Both actor and services on both client and handler sides have switched to use the new MethodNameProvider, which implements this new approach. Removed the base class CorrelatingProxyFactory as it seemed unnecessary after factoring out the method name provider into a separate class.