It seems that github uses a polling server for real time notifications (live.github.com) on its web interface.
It seems like the technology is not Websocket based neither XHR-polling.
How is it developed ?
A push service receives a network request, validates it and delivers a push message to the appropriate browser. If the browser is offline, the message is queued until the the browser comes online. Each browser can use any push service they want, it's something developers have no control over.
Statistics show that they have an 80% market reach, based on the number of browsers supporting web push (PushPushGo), with click-through rates typically seven times higher than email marketing, and opening rates 50% higher than email too (source: e-goi).
Push notifications are messages that pop up on a user's mobile phone or desktop device via their chosen web browser. These little banners slide into view — whether or not your app or website is open.
To use push notifications, you need to do two things: Set up your receiving URL, or "Webhook" callback receiver. This is an HTTPS server that handles the API notification messages that are triggered when a resource changes.
It seems they use HTML5 Server-Sent Events.
I found it after a while by looking at the request to live.github.com that accepts "text/event-stream"
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With