From bac31a50f17608c514afce5ad014316cccde3d5a Mon Sep 17 00:00:00 2001 From: David Robillard Date: Tue, 24 Jul 2007 21:23:22 +0000 Subject: Scrapped ClientKey in favour of a URI string (towards a simpler closer-to-straight-C engine interface). Fixed client deregistration. Added metadata value requesting. git-svn-id: http://svn.drobilla.net/lad/ingen@614 a436a847-0d15-0410-975c-d299462d15a1 --- src/common/interface/Responder.hpp | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) (limited to 'src/common/interface/Responder.hpp') diff --git a/src/common/interface/Responder.hpp b/src/common/interface/Responder.hpp index fc8cdcf7..0ae0972a 100644 --- a/src/common/interface/Responder.hpp +++ b/src/common/interface/Responder.hpp @@ -21,15 +21,11 @@ #include #include #include -#include "interface/ClientKey.hpp" #include "interface/ClientInterface.hpp" namespace Ingen { namespace Shared { -using Shared::ClientKey; -using Shared::ClientInterface; - /** Class to handle responding to clients. * @@ -39,8 +35,8 @@ using Shared::ClientInterface; * Note that this class only handles sending responses to commands from * clients, (ie OK or an error), not notifications (ie new node, * disconnection) - that's what ClientInterface is for. If a command is - * a request, the ClientKey of the Responder can be used to find the - * ClientInterface which should receive the response. + * a request, the Responder can be used to find the ClientInterface + * (by URI) which should receive the response. * * ClientInterface and Responder are seperate because responding might not * actually get exposed to the client interface (eg in simulated blocking @@ -57,8 +53,9 @@ public: Responder() {} virtual ~Responder() {} - virtual ClientKey client_key() { return ClientKey(); } - virtual SharedPtr client() { return SharedPtr(); } + virtual std::string client_uri() { return ""; } + + virtual SharedPtr client() { return SharedPtr(); } virtual void set_id(int32_t id) {} -- cgit v1.2.1