Skip to main content

Getting notifications of Network Status changes using online and offline events introduced in HTML5

I was working on an online\offline application, wherein I wanted to display a set of records stored in the local database to the user when he goes offline. The only way to determine the network status is to send a XHR request to the server at particular time intervals (polling). If the server responds back with some data it is understood that the user is online. However, I came across two event listeners 'ononline' and 'onoffline' which are triggered when the network status changes. Sample Code: These event listeners are not supported in every browser, I have tested this on Chrome 11 and it works great. Here is the code snippet that I have used in my application:
function showOnlineStatus() {     var status = document.getElementById('userStatus');     if(navigator.onLine)         status.innerHTML = status.className = 'online';     else         status.innerHTML = status.className = 'offline'; } window.onload = window.ononline = window.onoffline = showOnlineStatus;

As seen in the above code, the navigator object has an attribute onLine which is used to determine network status. It is set to true if the user is online and false otherwise. To test this, unplug the network cable and see that the offline event gets triggered. On connecting the network cable the online event would be triggered.
Labels:

Comments

  1. Cyril HanquezJune 9, 2011 at 12:19 AM

    Hi Sagar,

    sadly it's badly and differently supported by the browsers so I would not rely on it. Also if your router lose the internet connection, it won't be detected as the computer is still connected to the router.

    ReplyDelete
  2. RaymondJune 9, 2011 at 12:33 AM

    I think the point though is that it could be helpful. You could warn a user about them being offline - or use local storage to temporarily store stuff until they get back online.

    ReplyDelete
  3. Sagar GanatraJune 9, 2011 at 9:51 AM

    @Cyril,

    You're correct. This is not supported across the browsers (I have mentioned this in my post). However, once other browsers implement this feature we would not be facing this problem.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to use the APP_INITIALIZER token to hook into the Angular bootstrap process

I've been building applications using Angular as a framework of choice for more than a year and this post is not about another React vs Angular or the quirks of each framework. Honestly, I like Angular and every day I discover something new which makes development easier and makes me look like a guy who built something very complex in a matter of hours which would've taken a long time to put the correct architecture in place if I had chosen a different framework. The first thing that I learned in Angular is the use of the APP_INITIALIZER token.
Post a Comment
Read more

Using MobX to manage application state in a React application

I have been writing applications using React and Redux for quite some time now and thought of trying other state management solutions out there. It's not that I have faced any issues with Redux; however, I wanted to explore other approaches to state management. I recently came across MobX  and thought of giving it a try. The library uses the premise of  `Observables` to tie the application state with the view layer (React). It's also an implementation of the Flux pattern wherein it uses multiple stores to save the application state; each store referring to a particular entity. Redux, on the other hand, uses a single store with top-level state variables referring to various entities.
Post a Comment
Read more

On GraphQL and building an application using React Apollo

When I visualize building an application, I would think of using React and Redux on the front-end which talks to a set of RESTful services built with Node and Hapi (or Express). However, over a period of time, I've realized that this approach does not scale well when you add new features to the front-end. For example, consider a page that displays user information along with courses that a user has enrolled in. At a later point, you decide to add a section that displays popular book titles that one can view and purchase. If every entity is considered as a microservice then to get data from three different microservices would require three http  requests to be sent by the front-end app. The performance of the app would degrade with the increase in the number of http requests. I read about GraphQL and knew that it is an ideal way of building an app and I need not look forward to anything else. The GraphQL layer can be viewed as a facade which sits on top of your RESTful services o...
Post a Comment
Read more