17.4.1. Polling Model

The polling model continuously checks if an event has occurred — inefficient and outdated in most applications.

The polling model refers to a method where the program repeatedly checks or 'polls' for events or changes in state. Essentially, it keeps asking if something has happened, such as whether a user has clicked a button or whether data has arrived from a network source. This method is considered inefficient because it can use up unnecessary processing power while waiting for something to happen, making it less responsive than other models which react only when an event occurs.

Imagine a person waiting to see if the light turns green at a traffic signal. Instead of looking at the light and reacting when it changes, they continuously stare at the signal and note the color every second, even when nothing has changed. This is like the polling model, which regularly checks for changes instead of being alerted by the event itself.

This model is often seen as inefficient and outdated in most applications.

The key issue with the polling model is its inefficiency. For applications that require quick responses, such as real-time games or interactive user interfaces, constantly checking for events can cause lag and resource drain. This means that the system might miss quick changes or delays could occur. Newer event-handling models that utilize callbacks or interrupts are preferred because they allow the system to remain free for other tasks while waiting for an event to occur.

Think of the polling model as a waiter in a restaurant constantly checking at every table to see if patrons need anything. Instead of just waiting for customers to call them over when they need something, the waiter wastes time and energy moving from table to table. In contrast, a better system might involve the waiter only coming over when a bell rings, indicating a customer needs attention; this way, the waiter can focus on serving other customers efficiently.

--