X-Git-Url: http://g0dil.de/git?a=blobdiff_plain;f=Examples%2FUDPClientServer%2FMainpage.dox;h=b5c787580f5ee9c7633ad21e3b92597911a5c044;hb=34700cdc907e04dbe026df9e86d0509990706a31;hp=b36240419460efce8ee97f5d62b87264e815bf16;hpb=29825d5db542bd3a6769101abe40a8ed86409613;p=senf.git

diff --git a/Examples/UDPClientServer/Mainpage.dox b/Examples/UDPClientServer/Mainpage.dox
index b362404..b5c7875 100644
--- a/Examples/UDPClientServer/Mainpage.dox
+++ b/Examples/UDPClientServer/Mainpage.dox
@@ -65,16 +65,17 @@
     Scheduler. The <tt> \link senf::Scheduler::add add() \endlink </tt> 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 <a href="http://www.boost.org/doc/html/function.html">Boost.Function</a> 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 <a href="http://www.boost.org/doc/libs/release/doc/html/function.html">
+    Boost.Function</a> 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 }
 
     Calling the Schedulers <tt> \link senf::Scheduler::process process()\endlink </tt> method will
-    start the event loop. This call does not return (ok, it does return in special cases if 
-    \c senf::Scheduler::terminate() is called which does not apply here). The Callback Function is 
+    start the event loop. This call does not return (ok, it does return in special cases if
+    \c senf::Scheduler::terminate() is called which does not apply here). The Callback Function is
     the \c readFromClient() Function, which is declared as private here and will be called whenever
     an event on the socket is encountered. The scheduler passes the event ID to the function.
 
@@ -106,13 +107,13 @@
 
     First a \c ::UDPv4ClientSocketHandle is created. With the function
     \c writeto(senf::INet4SocketAddress, string) the string s will be written to the specified
-    address and port, which is constructed here from a  static string \c "127.0.0.1:4243". In this
+    address and port, which is constructed here from a  static string read from the console with the format \c IP:PORT. In this
     example Integers from zero to ten are send to the Server socket.
 
     The exception handling is again the same as with the server application.
 */
 
-
+
 // Local Variables:
 // mode: c++
 // fill-column: 100