X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=Examples%2FUDPClientServer%2FMainpage.dox;h=b5c787580f5ee9c7633ad21e3b92597911a5c044;hb=34700cdc907e04dbe026df9e86d0509990706a31;hp=49043d8c1578f666edbd8f47c1f2a38cb7552b51;hpb=9cb871b939efe93e35dd96808d25089399acfc46;p=senf.git
diff --git a/Examples/UDPClientServer/Mainpage.dox b/Examples/UDPClientServer/Mainpage.dox
index 49043d8..b5c7875 100644
--- a/Examples/UDPClientServer/Mainpage.dox
+++ b/Examples/UDPClientServer/Mainpage.dox
@@ -65,10 +65,11 @@
Scheduler. The \link senf::Scheduler::add add() \endlink call takes two Arguments,
the socket to bind to (which can be a lot of things and must not necessarily be a socket
instance) and callback function to call, whenever there is an event on that socket.The callback
- is specified as a Boost.Function object.
- A third argument may be specified to restrict the events, on which the function is called, here we
- used the EV_READ Argument, because we just want the program to read from the socket.
- The default argument is set to \c senf::Scheduler::EV_ALL, which allows all actions on the socket.
+ is specified as a
+ Boost.Function object. A third argument may be specified to restrict the events, on which
+ the function is called, here we used the EV_READ Argument, because we just want the program to
+ read from the socket. The default argument is set to \c senf::Scheduler::EV_ALL, which allows
+ all actions on the socket.
\until }