Home > Articles > Programming > C/C++

  • Print
  • + Share This
Like this article? We recommend

EventHandler Class

Listing 2 contains a constructor that sets the member properties to null default values. The member function HasEventSupport() indicates whether the object of this class provides event support. The chain of responsibility pattern allows objects to either provide support or to pass the event along to the _successor object. If the object of this class wants to provide a specific event handler, it calls SetHandler(EventHandler*, Event). The last member function is HandleEvent(), which is used to implement the event handler. Two member properties are provided in the EventHandler base class: _successor and _event. The _successor is a pointer to the next handler in the chain or responsibility; that is, if I don’t handle the event, I pass it on the _successor. The event in question is stored in the _event variable.

Let’s now see how this base class is used to provide the chain of responsibility.

Connection Subclass of EventHandler

Given that we’re using a devolved model for event management, we now define a Connection class in Listing 3. Remember the LSP (LSP123) in Figure 1? Well, this is an EventHandler subclass to represent such logical connections.

Listing 3 Connection: A Derived Class of EventHandler

class Connection : public EventHandler {
   Connection(Event t) : EventHandler(0, t) { }

   virtual void HandleEvent(); };

void Connection ::HandleEvent() { }

class Path : public Connection {
   Path::Path(Connection* w, Event t) : Connection(0) {
      cout << "In the Path constructor\n";
      SetHandler(w, t);   }

Connection is a generic subclass of EventHandler. I say generic because Connection can be used (via inheritance) to model any type of logical network connection, such as LSPs, IP tunnels, and so on. Just think of it as a placeholder for more specialized subclasses in the same way as "Human" is a generic placeholder type for "Male" and "Female".

Listing 3 defines another class called Path derived from Connection. Path is a means of storing a route for an LSP (such as LSP123, which follows the route R2-R3-R4-R5 in Figure 1). Listing 4 illustrates the last class of interest to us: the Lsp class derived from Connection.

Listing 4 Lsp Class: A Specific Connection Subclass

class Lsp : public Connection {
   Lsp::Lsp(char* lspID, Connection* w, Event t) : Connection(0) {
      lspName = lspID;
      SetHandler(w, t); 	}

   void HandleEvent() {
      if (HasEventSupport()) {
         cout << "\nAt last, here’s some LSP Event support:\n";
         cout << "We need more bandwidth on " << lspName << "\n\n";
         EventHandler::HandleEvent();	}
   char* lspName; };

The Lsp class acquires (via inheritance) all the capabilities of EventHandler as well as adding a few wrinkles of its own. As you can see, Lsp implements the HandleEvent() member function. This member function is defined as virtual in the EventHandler base class, so subclasses are free to define it as required. In the case of the Lsp class, the event support provided is to print out an informative message.

Now let’s put it all together and build the chain of responsibility, as illustrated in Listing 5 (repeated from Listing 1).

Listing 5 The Chain of Responsibility

   Connection* connection = new Connection(No_Event_Support);
   Lsp* lsp = new Lsp("LSP_IPTV0001", connection, LINK_1A_CONGESTION);
   Path* path = new Path(lsp, No_Event_Support);

At the top of the chain is a Connection* object. The next level in the chain is an Lsp* object. Finally, at the bottom of the chain is a Path* object. To start the event processing, we simply call path->HandleEvent().

This simulates our link failure from Figure 1. Listing 6 illustrates part of the program output (excluding initialization in the constructors).

Listing 6 Program Output

No support from Path - Sorry!
Calling the base class event handler
HandleEvent () calling into successor
At last, here’s some LSP Event support:
We need a new path for LSP123

The first line of Listing 6 shows us that the path object can’t offer any help because the Path class implements a very thin HandleEvent() method. So because the path object can’t process the event, it calls the base class HandleEvent() method, which then results in a call to the Lsp HandleEvent() method. As the second-to-last line in Listing 6 illustrates, we finally get some help from this object in the form of a message indicating that we need a new path for the LSP (LSP123) that traverses the (now) broken link in Figure 1.

That’s it! That’s our chain of responsibility passing the event around like a hot potato until an appropriate handler is found. It’s a little like someone in a crowded room saying, "Is anyone here a doctor?"

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020