aboutsummaryrefslogtreecommitdiff
path: root/src/client.cpp
diff options
context:
space:
mode:
authorMike Buland <eichlan@xagasoft.com>2009-01-11 23:07:44 +0000
committerMike Buland <eichlan@xagasoft.com>2009-01-11 23:07:44 +0000
commit1291252a7b1317ad2dc13fbeb15f6e9d2d92192c (patch)
tree5eb88c7cef5417c043b03b34a77334c57286e526 /src/client.cpp
parent595afe519791894c77c77a949fba7732f4d94872 (diff)
downloadlibbu++-1291252a7b1317ad2dc13fbeb15f6e9d2d92192c.tar.gz
libbu++-1291252a7b1317ad2dc13fbeb15f6e9d2d92192c.tar.bz2
libbu++-1291252a7b1317ad2dc13fbeb15f6e9d2d92192c.tar.xz
libbu++-1291252a7b1317ad2dc13fbeb15f6e9d2d92192c.zip
A new feature has been added to Bu::Server. It's going to be trickier to
implement in Bu::ItoServer, but I'll get to it. Basically you can trigger a "tick" any time you want and it will propegate as an onTick event to all active clients. You can also have these generated automatically everytime the system passes through a polling cycle. In this case, you should never ever write data to the socket every tick. It will cause your program to go bursurk.
Diffstat (limited to '')
-rw-r--r--src/client.cpp6
1 files changed, 6 insertions, 0 deletions
diff --git a/src/client.cpp b/src/client.cpp
index 0ab0618..81f2285 100644
--- a/src/client.cpp
+++ b/src/client.cpp
@@ -247,3 +247,9 @@ void Bu::Client::onMessage( const Bu::FString &sMsg )
247 pProto->onMessage( this, sMsg ); 247 pProto->onMessage( this, sMsg );
248} 248}
249 249
250void Bu::Client::tick()
251{
252 if( pProto )
253 pProto->onTick( this );
254}
255