Great, but as I understand from these bugs: https://bugs.opendaylight.org/show_bug.cgi?id=6310 https://bugs.opendaylight.org/show_bug.cgi?id=3128
Global RPC today has a bug that it is not routed to the nearest registered implementation inside a cluster, and therefore I need to use a RoutedRPC as a workaround. Right? -----Original Message----- From: Robert Varga [mailto:n...@hq.sk] Sent: Tuesday, November 29, 2016 2:44 PM To: Sela, Guy <guy.s...@hpe.com>; Muthukumaran K <muthukumara...@ericsson.com>; controller-dev@lists.opendaylight.org; mdsal-...@lists.opendaylight.org Subject: Re: [controller-dev] Global RPCs aren't delegated in a cluster? On 11/29/2016 01:15 PM, Sela, Guy wrote: > Are you trying to argue that there is no real meaning to the "globality" > of Global RPC because theoretically someone could register it in a > number of nodes? > > Isn't this the same case with RoutedRpc that different nodes can > register for the same path? Naming pre-dates RFC7950. To simplify things: "Global RPC" == RFC7950 rpc "Routed RPC" == RFC7950 action (except we modeled it on top of rpc) >From application perspective and routing within a cluster, both should behave >the same, i.e. requests are routed to the nearest registered implementation, >be it the local node or some remote node. It is not prohibited to have >multiple implementations registered for either at any given time. Regards, Robert _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
