Push notifications are small messages that can reach audiences anywhere and anytime. There’s a difference between pop-ups and push notifications. Pop-ups appear only when audiences are on the site they belong to. Push messages are independent of sites. They are associated with web browsers and apps.
Push technology, or server push, is a style of Internet-based communication where the request for a given transaction is initiated by the publisher or central server. It is contrasted with pull/get, where the request for the transmission of information is initiated by the receiver or client.
Push services are often based on information preferences expressed in advance. This is called a publish/subscribe model. A client "subscribes" to various information "channels" provided by a server; whenever new content is available on one of those channels, the server pushes that information out to the client.
Push is sometimes emulated with a polling technique, particularly under circumstances where a real push is not possible, such as sites with security policies that require rejection of incoming HTTP/S requests.
Synchronous conferencing and instant messaging are typical examples of push services. Chat messages and sometimes files are pushed to the user as soon as they are received by the messaging service. Both decentralised peer-to-peer programs (such as WASTE) and centralised programs (such as IRC or XMPP) allow pushing files, which means the sender initiates the data transfer rather than the recipient.
Email may also be a push system: The SMTP protocol is a push protocol (see Push e-mail). However, the last step—from mail server to desktop computer—typically uses a pull protocol like POP3 or IMAP. Modern e-mail clients make this step seem instantaneous by repeatedly polling the mail server, frequently checking it for new mail. The IMAP protocol includes the IDLE command, which allows the server to tell the client when new messages arrive. The original BlackBerry was the first popular example of push-email in a wireless context.
Another example is the PointCast Network, which was widely adopted in the 1990s. It delivered news and stock market data as a screensaver. Both Netscape and Microsoft integrated push technology through the Channel Definition Format (CDF) into their software at the height of the browser wars, but it was never very popular. CDF faded away and was removed from the browsers of the time, replaced in the 2000s with RSS (a pull system.)
Other uses of push-enabled web applications include software updates distribution ("push updates"), market data distribution (stock tickers), online chat/messaging systems (webchat), auctions, online betting and gaming, sport results, monitoring consoles, and sensor network monitoring.
The Webpush proposal of the Internet Engineering Task Force is a simple protocol using HTTP version 2 to deliver realtime events, such as incoming calls or messages, which can be delivered (or “pushed”) in a timely fashion. The protocol consolidates all real-time events into a single session which ensures more efficient use of network and radio resources. A single service consolidates all events, distributing those events to applications as they arrive. This requires just one session, avoiding duplicated overhead costs.
Web Notifications are part of W3C standard and defines an API for end-user notifications. A notification allows alerting the user outside the context of a web page of an occurrence, such as the delivery of email.  As part of this standard Push API defined by W3C, is now being implemented by Chrome, Firefox, Edge, and Safari.
HTTP server push
HTTP server push (also known as HTTP streaming) is a mechanism for sending unsolicited (asynchronous) data from a web server to a web browser. HTTP server push can be achieved through any of several mechanisms.
Generally the web server does not terminate a connection after response data has been served to a client. The web server leaves the connection open so that if an event occurs (for example, a change in internal data which needs to be reported to one or multiple clients), it can be sent out immediately; otherwise, the event would have to be queued until the client's next request is received. Most web servers offer this functionality via CGI (e.g., Non-Parsed Headers scripts on Apache HTTP Server). The underlying mechanism for this approach is chunked transfer encoding.
Another mechanism is related to a special MIME type called
multipart/x-mixed-replace, which was introduced by Netscape in 1995. Web browsers interpret this as a document changing whenever the server feels like pushing a new version to the client. It is still supported by Firefox, Opera, and Safari today, but it is ignored by Internet Explorer. It can be applied to HTML documents, and also for streaming images in webcam applications.
The WHATWG Web Applications 1.0 proposal includes a mechanism to push content to the client. On September 1, 2006, the Opera web browser implemented this new experimental system in a feature called "Server-Sent Events". It is now being standardized as part of HTML5.
Long polling is itself not a true push; long polling is a variation of the traditional polling technique, but it allows emulating a push mechanism under circumstances where a real push is not possible, such as sites with security policies that require rejection of incoming HTTP/S Requests.
With long polling, the client requests information from the server exactly as in normal polling, but with the expectation the server may not respond immediately. If the server has no new information for the client when the poll is received, instead of sending an empty response, the server holds the request open and waits for response information to become available. Once it does have new information, the server immediately sends an HTTP/S response to the client, completing the open HTTP/S Request. Upon receipt of the server response, the client often immediately issues another server request. In this way the usual response latency (the time between when the information first becomes available and the next client request) otherwise associated with polling clients is eliminated.
For example, BOSH is a popular, long-lived HTTP technique used as a long-polling alternative to a continuous TCP connection when such a connection is difficult or impossible to employ directly (e.g., in a web browser); it is also an underlying technology in the XMPP, which Apple uses for its iCloud push support.
Flash XMLSocket relays
Reliable Group Data Delivery (RGDD)
In services such as Cloud Computing, to increase reliability and availability of data, it is usually pushed (replicated) to several machines. For example, the Hadoop Distributed File System (HDFS) makes 2 extra copies of any object stored. RGDD focuses on efficiently casting an object from one location to many while saving bandwidth by sending minimal number of copies (only one in the best case) of the object over any link across the network. For example, Datacast  is a scheme for delivery to many nodes inside datacenters that relies on regular and structured topologies and DCCast  is a similar approach for delivery across datacenters.
A push notification is a message that is "pushed" from backend server or application to user interface, e.g. (but not limited to) mobile applications and desktop applications. Push notifications were first introduced by Apple in 2009. In 2010 Google released its own service, Google Cloud to Device Messaging. (It has since been replaced by Google Cloud Messaging and then Firebase Cloud Messaging.) November 2015, Microsoft announced that the Windows Notification Service would be expanded to make use of the Universal Windows Platform architecture, allowing for push data to be sent to Windows 10, Windows 10 Mobile, Xbox, as well as other supported platforms using universal API calls and POST requests.
Push notifications are mainly divided into 2 approaches, local notifications and remote notifications. For local notifications, the application schedules the notification with the local device's OS, or, alternatively, sets as a timer in the application itself if it is able to continuously run in the background. When the event's scheduled time is reached, or the event's programmed condition is met, the message is displayed in the application's user interface.
Remote notifications are handled by a remote server. Under this scenario, the client application needs to be registered on the server with a unique key (e.g., a UUID). The server then fires the message against the unique key to deliver the message to the client application via an agreed client/server protocol such as HTTP or XMPP and the client displays the message received. When the push notification arrives, it can transmit short notifications and messages, set badges on application icons or play alert sounds to attract user's attention. Push notifications are usually used by applications to bring information to users' attention. The content of the messages can be classified in the following example categories:
- Chat messages. E.g.: messages from Facebook messenger sent by other users.
- Vendor special offers. E.g.: A vendor may want to advertise their social offers to the customers.
- Event reminder. E.g.: Some application may allow the customer to create reminder or alert for a specific time.
- Subscribed topics changes. E.g.: Users may want to get updates regarding the weather in their location, or monitor a web page to track changes, for instance.
- Channel Definition Format
- Client–server model
- File transfer
- Pull technology
- Push Access Protocol
- Push e-mail
- SQL Server Notification Services
- Streaming media
- "What is push notifications & How do push notifications work?". www.pushmaze.com. Retrieved 2018-10-25.
- M. Thomson, E. Damaggio and B. Raymor (October 22, 2016). "Generic Event Delivery Using HTTP Push". Internet Draft. Internet Engineering Task Force. Retrieved October 28, 2016.
- "Web Notifications".
- "Web Push API".
- CGI Programming on the World Wide Web O'Reilly book explaining how to use Netscape server-push
- Server-Push Documents (HTML & XHTML: The Definitive Guide) Archived 2008-04-17 at the Wayback Machine. O'Reilly book explaining server-push
- "Web Applications 1.0 specification".
- "Event Streaming to Web Browsers". 2006-09-01. Retrieved 2007-03-23.
- "Opera takes the lead with AJAX support among browsers: More efficient streaming". 2006-09-01. Archived from the original on 2007-03-18. Retrieved 2007-03-23.
- Server-Sent Events
- Pushlets introduction
- JavaWorld article about pushlets
- "RFC6202 - Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP". Retrieved 2016-05-14.
- "XEP-0124: Bidirectional-streams Over Synchronous HTTP (BOSH)". Retrieved 2012-06-26.
- C. Guo; et al. (November 1, 2012). "Datacast: A Scalable and Efficient Reliable Group Data Delivery Service For Data Centers". ACM. Retrieved Jun 6, 2017.
- M. Noormohammadpour; et al. (July 10, 2017). "DCCast: Efficient Point to Multipoint Transfers Across Datacenters". USENIX. Retrieved Jun 6, 2017.
- "iPhone push notification service for devs announced". Engadget. Retrieved 2016-10-18.
- "Google Cloud Messaging for Android (GCM) Unveiled, to Replace C2DM Framework". InfoQ. Retrieved 2016-10-18.
- mijacobs. "Windows Push Notification Services (WNS) overview". docs.microsoft.com. Retrieved 2017-10-20.
- "Local and Remote Notifications in Depth". developer.apple.com. Retrieved 2016-10-18.
- "Android and iOS Push Notifications – Blog – JatApp". jatapp.com. Retrieved 2017-10-20.
- "How do I adjust my mobile push notifications from Facebook? | Facebook Help Center | Facebook". www.facebook.com. Retrieved 2016-10-18.