Home > Articles > Programming > PHP

This chapter is from the book

Comparing Technologies

Before even starting to think about code layout, there's a phase we don't know what else to call but "getting things together." This is the intermediate step between the idea and the specs/code layout stage—figuring out the inner workings and on what to base them.

To make it clearer, let's go back to the very beginning:

  • What do we want to create?

  • How are we going to create it?

  • Are there any existing implementations of our idea already?

  • Do similar systems exist that perform almost the same task?

  • If so, can we reuse anything from that design?

  • Can we reuse foreign techniques, maybe add up to our system with them?

Questions over questions.

The first is easy to answer. We want to create a chat system. How? Well, with PHP, and somehow server-side—we don't know much more about it at this time.

Are there already any chat systems or something similar out there? Indeed there are. It starts right at your shell—the "talk" command allows you to chat with other people that you can reach via a valid network link (or local link), as shown in Figure 3.1.

03fig01a.gifFigure 3.1. The traditional "talk" command.

Of course, this isn't as powerful as we'd want it to be, but it's a start. Next, we could surf the Web to look for pages that have one of the (nowadays almost obligatory) chat links. Although they differ widely in look and feel/implementation, most of them can be boiled down to the following:

  • Java for fancy interfaces, although some use plain HTML.

  • A proprietary protocol with a single server (or simply database-backed).

  • Few predefined rooms.

  • Few predefined commands.

Apart from these chat setups, there are chat applications and networks such as Mirabilis' ICQ or the diverse Instant Messaging Systems—systems that don't always provide real-time services and generally require additional proprietary client software to be installed on every participating system.

However, one system stands out from the list. IRC (Internet Relay Chat) is a widely-known and long-used chat protocol used by many networks, some of which carry hundreds of thousands of users simultaneously. The IRC protocol is text-based—a drawback when operating under high load (long string commands generate much more traffic than single binary characters), but this also makes it significantly easier to process. Most current IRC servers support compressed backbone links, which greatly reduce traffic.

Although IRC requires special client software on every participating system, we can "tweak" this requirement to our advantage: Why not provide the client software ourselves server-side, and abstract it by using an HTML interface and allowing each user access to the network through an HTML client? This would give us control over what the user can do (each user is required to use our HTML client). Additionally, we have all the advantages of an existing network system: reliable client software, proven concept, hundreds of tools, etc. We could even allow users to use their own client software—an option to be avoided in most cases, however, as we want to create a "closed" chat network. On a closed network, you know every way that each client can access your network. By limiting the access points to specific setups, you greatly reduce the risk of being attacked.

This directly leads to the question, do we need a real protocol such as IRC? Or would it be sufficient to simply use a database-driven protocol, with a remote synchronization feature to provide the requested networking abilities?

Questions such as this will arise every time you plan an application, and they'll arise often. Make sure that you've got all of them covered, and make sure that no questions will arise at a later stage during development. This is the point where you can still address these questions; later on you might be unable to resolve them (and eventually get your project kicked into the trash). A good project is a project without doubts, without uncertainties, without inconsistencies, and without unforeseen eventualities. Make sure that after your planning phase you can assure a stable, fully evaluated situation!

So let's get back to answering the question: Do we need an open (and perhaps too complex) protocol such as IRC, or should we stick with a conventional database approach? The simplest method to find an answer is also the most logical one—compare pros and cons and choose the option with the best results.

Implementing IRC as a protocol into the chat system will introduce a significant amount of complication because of protocol processing—processing network protocols requires nonlinear coding, something that isn't really supported by PHP. (To react to network messages, we need an event-based system.) On top of that problem, we'd need a way to handle message exchange efficiently; that is, dealing with messages from a user and for a user (which, unfortunately, may not always be handled in the same way). This problem exists in the database-backed solution, too, of course, but the database-backed solution doesn't require protocol handling. A lot of databases are supported natively by PHP, and those that aren't are most likely supported indirectly by ODBC. To gain the ability of networkable chat boxes, we'd only need to create a tool that can synchronize between chat boxes. (Unless you only want to run one central database server that's accessed by all boxes simultaneously.)

What would you choose?

Spoiler: phpChat is based on IRC, and this is why:

  • Using a database, we'd introduce some kind of "proprietary," private protocol that wouldn't be able to interface to other standard systems. In times of interoperability and interconnectivity, this is a bad thing.

  • An IRC library that functions well (namely phpIRC, see http://www.phpwizard.net/phpIRC) abstracts access to IRC networks into a set of easy-to-use API functions—and makes IRC handling equal to database handling in terms of code complexity.

  • Existing IRC server software handles all the itsy-bitsy teenie-weenie problems of user management, reliable traffic forwarding, routing, etc., across networks. The software has been around for a long time and is proven to work, plus it's available for all types of systems.

  • IRC is extremely scalable. If you run into load problems on server A at peak times or due to unforeseen events, simply fire up server B and dynamically establish a server connection into the existing chat (IRC allows you to do so, and is fully automated)—and you now have another server with enough free capacity for additional users.

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