Changes between Version 10 and Version 11 of OverSimDevelop

Timestamp:

Aug 15, 2008, 4:21:15 PM (16 years ago)

Author:

heep

Comment:

--

OverSimDevelop

@@ -16 +16 @@
 == 1. Implementing new overlay modules in !OverSim ==
 
-This is a guide to implement new overlay modules for !OverSim. It is aimed to be an introductory guide, for more in-depth information you should consult the links provided in Section 1. This guide is divided as follows. In order to understand the place an overlay module takes inside nodes and how it interacts with them, first the module hierarchy for overlay hosts is described. Then we proceed to explain how overlay modules should declared using the NED language. Next, the basics for the module implementation are described using the base class BaseOverlay. Finally we explain how to make !OverSim compile and run your module.
+This is a guide to implement new overlay modules for !OverSim. It is aimed to be an introductory guide, for more in-depth information you should consult the doxygen documentation. This guide is divided as follows. In order to understand the place an overlay module takes inside nodes and how it interacts with them, first the module hierarchy for overlay hosts is described. Then we proceed to explain how overlay modules should declared using the NED language. Next, the basics for the module implementation are described using the base class BaseOverlay. Finally we explain how to make !OverSim compile and run your module.
 
 == 2. !OverSim nodes ==
@@ -43 +43 @@
         in: from_app;    // gate from the application
         out: to_app;     // gate to the application
+        in: direct_in;   // gate for sendDirect
 endsimple
 }}}
 
-The module declaration is divided in two subsections: parameters and gates. The parameters subsection contains custom parameters established by the user, while the gates subsection establishes the connections to the other layers: from_udp and to_udp to the UDP layer, and from_app and to_app to the application layer. 
+The module declaration is divided in two subsections: parameters and gates. The parameters subsection contains custom parameters established by the user, while the gates subsection establishes the connections to the other layers: from_udp and to_udp to the UDP layer, and from_app and to_app to the application layer. The direct_in gate is used for e.g. internal RPCs.
 
 Modules can be nested inside one another. Modules without any inner modules are called simple modules, and are declared using the keyword simple. Only simple modules can have its behaviour customized with C++ (see Section 4). On the other hand, modules with inner nested modules are called compound modules, and act only as containers; they are declared with the keyword module.