Txc5 Class Reference

Inheritance diagram for Txc5:

List of all members.

---

Detailed Description

In the previous models, `tic' and `toc' immediately sent back the received message. Here we'll add some timing: tic and toc will hold the message for 1 simulated second before sending it back. In OMNeT++ such timing is achieved by the module sending a message to itself. Such messages are called self-messages (but only because of the way they are used, otherwise they are completely ordinary messages) or events. Self-messages can be "sent" with the scheduleAt() function, and you can specify when they should arrive back at the module.

We leave out the counter, to keep the source code small.

Public Member Functions
	Txc5 ()
virtual	~Txc5 ()
Protected Member Functions
virtual void	initialize ()
virtual void	handleMessage (cMessage *msg)
Private Attributes
cMessage *	event
cMessage *	tictocMsg

---

Constructor & Destructor Documentation

Txc5::Txc5 (   )

{ // Set the pointer to NULL, so that the destructor won't crash // even if initialize() doesn't get called because of a runtime // error or user cancellation during the startup process. event = tictocMsg = NULL; }

Txc5::~Txc5 (   )  [virtual]

{ // Dispose of dynamically allocated the objects cancelAndDelete(event); delete tictocMsg; }

---

Member Function Documentation

void Txc5::handleMessage (  cMessage *  msg  )  [protected, virtual]

Reimplemented from cSimpleModule. { // There are several ways of distinguishing messages, for example by message // kind (an int attribute of cMessage) or by class using dynamic_cast // (provided you subclass from cMessage). In this code we just check if we // recognize the pointer, which (if feasible) is the easiest and fastest // method. if (msg==event) { // The self-message arrived, so we can send out tictocMsg and NULL out // its pointer so that it doesn't confuse us later. ev << "Wait period is over, sending back message\n"; send(tictocMsg, "out"); tictocMsg = NULL; } else { // If the message we received is not our self-message, then it must // be the tic-toc message arriving from our partner. We remember its // pointer in the tictocMsg variable, then schedule our self-message // to come back to us in 1s simulated time. ev << "Message arrived, starting to wait 1 sec...\n"; tictocMsg = msg; scheduleAt(simTime()+1.0, event); } }

void Txc5::initialize (   )  [protected, virtual]

Reimplemented from cModule. { // Create the event object we'll use for timing -- just any ordinary message. event = new cMessage("event"); // No tictoc message yet. tictocMsg = NULL; if (strcmp("tic", name()) == 0) { // We don't start right away, but instead send an message to ourselves // (a "self-message") -- we'll do the first sending when it arrives // back to us, at t=5.0s simulated time. ev << "Scheduling first send to t=5.0s\n"; tictocMsg = new cMessage("tictocMsg"); scheduleAt(5.0, event); } }

---

Member Data Documentation

cMessage* Txc5::event [private]

cMessage* Txc5::tictocMsg [private]

---

The documentation for this class was generated from the following file:

• txc5.cc

---