Wowee, I think all this new stuff works, Conduit I don't need now, so it's not

done yet.  The Client class now supports a function called getLink() which
returns a ClientLink object.  This object may then be passed off to any other
class and called to send messages to that client object. It is threadsafe if
ItoServer is being used, and not for Server.  Sending a message via a
ClientLink calls the onMessage function on the assosiated protocol.

Note that sending messages from within protocol event handlers or functions they
call, while safe, may be slow and it's reccomended that you avoid this.

1 files changed, 17 insertions, 2 deletions

diff --git a/src/client.cpp b/src/client.cpp
index 1ef9151..d1eb29c 100644
--- a/src/client.cpp
+++ b/src/client.cpp
@@ -11,15 +11,18 @@
 #include <errno.h>
 #include "bu/exceptions.h"
 #include "bu/protocol.h"
+#include "bu/clientlink.h"
+#include "bu/clientlinkfactory.h"
 
 /** Read buffer size. */
 #define RBS             (1024*2)
 
-Bu::Client::Client( Bu::Socket *pSocket ) :
+Bu::Client::Client( Bu::Socket *pSocket, class Bu::ClientLinkFactory *pfLink ) :
         pSocket( pSocket ),
         pProto( NULL ),
         nRBOffset( 0 ),
-        bWantsDisconnect( false )
+        bWantsDisconnect( false ),
+        pfLink( pfLink )
 {
 }
 
@@ -233,3 +236,15 @@ void Bu::Client::close()
 {
         pSocket->close();
 }
+
+Bu::ClientLink *Bu::Client::getLink()
+{
+        return pfLink->createLink( this );
+}
+
+void Bu::Client::onMessage( const Bu::FString &sMsg )
+{
+        if( pProto )
+                pProto->onMessage( this, sMsg );
+}
+