Enhancements to remote rpc server. Using zmq router-dealer bridge to make the server...

Enhancements to remote rpc client. Using zmq router-dealer bridge to make the client async.
Added configuration for remote rpc in Configuration subsystem
On Server startup reading of routingtable to populate remoterpcs was giving exception - fixed the same
Client was not registered with Server and addRPCImplementation was failing - fixed the same
ServerImpl was not getting registered as listener to RoutingTable hence announcement was not received on remote - fixed the same
Patch 6: Some unit tests were intemittently hanging. ZMQ Test server was not gracefully shutting down.

Change-Id: I6054443b39394f82258522205ccd4be470f597f0
Signed-off-by: Basheeruddin Ahmed <syedbahm@cisco.com>
Signed-off-by: Abhishek Kumar <abhishk2@cisco.com>

diff --git a/opendaylight/md-sal/sal-dom-api/src/main/java/org/opendaylight/controller/sal/core/api/RpcRoutingContext.java b/opendaylight/md-sal/sal-dom-api/src/main/java/org/opendaylight/controller/sal/core/api/RpcRoutingContext.java
new file mode 100644 (file)
index 0000000..1680c19
--- /dev/null
+++ b/opendaylight/md-sal/sal-dom-api/src/main/java/org/opendaylight/controller/sal/core/api/RpcRoutingContext.java
@@ -0,0 +1,18 @@
+/*
+ * Copyright (c) 2014 Cisco Systems, Inc. and others.  All rights reserved.
+ *
+ * This program and the accompanying materials are made available under the
+ * terms of the Eclipse Public License v1.0 which accompanies this distribution,
+ * and is available at http://www.eclipse.org/legal/epl-v10.html
+ */
+
+package org.opendaylight.controller.sal.core.api;
+
+import org.opendaylight.yangtools.yang.common.QName;
+
+public interface RpcRoutingContext {
+
+  public QName getContext();
+
+  public QName getRpcType();
+}