Changes between Version 29 and Version 30 of Documentation/Tutorial/PingPong

Timestamp:

Apr 28, 2009, 4:14:04 PM (15 years ago)

Author:

huebsch

Comment:

--

Documentation/Tutorial/PingPong

@@ -137 +137 @@
 After definitions for construction und destruction (the first also setting a timer to 5 seconds), we come to the ''startup'' method.
 The ''startup'' method (lines 20 ff.) is called from the !StartupWrapper, jolting the operation of the ping pong service. Here, we first create an AribaModule object, serving as our port to ''Ariba'' (line 33). Then, we give our network instance a specific name (being ''spovnet'' in the example), before we collect some configurational parameters (lines 46-56). Those parameters are defined in the config file, they serve e.g. in giving IP adresses and port numbers to ariba instances. In line 56, we start ''Ariba''. Also, we need a ''Node'' object, reflecting our application running over ''Ariba'' (more than one could possibly be using one Ariba). This is created in line 62 and the bound to the ariba object with its specific ServiceID. After this bnind operation, the ''Node'' is able to receive signals and messages from ''Ariba''. After this, we start the node object and either initiate or join the network instance (depending on the role of the actual node, wich could be initiator or joiner). 
-Finally, we may give out all kinds of logging infos by calling the method logging_info (line 47).
+Finally, we may give out all kinds of logging infos by calling the method logging_info (line 76).
  
 
 {{{
-60 void PingPong::shutdown(){
-61      logging_info( "shutting down PingPong service ..." );
-62
-63      overlay->unbind( this, PingPong::PINGPONG_ID );
-64      Timer::stop();
-65
-66      if( !startping ) abstraction->destroySpoVNet( context );
-67      else             abstraction->leaveSpoVNet( context );
-68
-69      logging_info( "PingPong service shut down" );
-70 }
-}}}
-
-To shut a service down after its usage, every service provides a method ''shutdown'' which is automatically called upon finishing (lines 60-70). In here, we unbind the service, stop any timers (mentioned later) and finally leave leave or destroy the SpoVNet instance, depending on the specific node's role. 
-
+01 void PingPong::shutdown() {
+02
+03      logging_info( "pingpong service starting shutdown sequence ..." );
+04
+05      // stop timer
+06      Timer::stop();
+07
+08      // leave spovnet
+09      node->leave();
+10
+11      // unbind communication and node listener
+12      node->unbind( this );                               /*NodeListener*/
+13      node->unbind( this, PingPong::PINGPONG_SERVICEID ); /*CommunicationListener*/
+14
+15      // stop the ariba module
+16      ariba->stop();
+17
+18      // delete node and ariba module
+19      delete node;
+20      delete ariba;
+21
+22      // now we are completely shut down
+23      logging_info( "pingpong service shut down" );
+24}
+}}}
+
+To shut a service down after its usage, every service provides a method ''shutdown'' which is automatically called upon finishing. In here, we stop the timer, leave the instance, unbind all bindings and finally stop the node and ''Ariba''. Don't forget to delete yopur objects to prevent from memory leaks.
 
 {{{