summaryrefslogtreecommitdiff
path: root/src/protocol.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/protocol.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 'src/protocol.cpp')
-rw-r--r--src/protocol.cpp12
1 files changed, 12 insertions, 0 deletions
diff --git a/src/protocol.cpp b/src/protocol.cpp
index 51ff105..b0efc07 100644
--- a/src/protocol.cpp
+++ b/src/protocol.cpp
@@ -17,7 +17,19 @@ Bu::Protocol::~Protocol()
17{ 17{
18} 18}
19 19
20void Bu::Protocol::onNewConnection( Bu::Client * )
21{
22}
23
24void Bu::Protocol::onNewData( Bu::Client * )
25{
26}
27
20void Bu::Protocol::onMessage( Bu::Client *, const Bu::FString & ) 28void Bu::Protocol::onMessage( Bu::Client *, const Bu::FString & )
21{ 29{
22} 30}
23 31
32void Bu::Protocol::onTick( Bu::Client * )
33{
34}
35