wq/online Android Issue about wq.app HOT 2 CLOSED

I agree, we need a more robust check than what navigator.onLine provides. I've also wanted to handle the case where onLine is "true" but there isn't actually a connection all the way to the internet. While we're at it, it would be nice to check latency so we could have a configurable cutoff point. For example, if the connection is working but very slow, we might want to count it as offline to speed things up. "slow" might be different depending on what we need the connection for.

I think an AJAX request makes sense, though we'll need to figure out where to send it (static file? add a "ping" service to wq.db? always require user to set a url?).

Here are some steps toward resoving this:

• Do some investigating to find out what is currently being done to address this issue (http://offlinefirst.org/ could be a starting point). There may even be a library that handles this problem.
• Assuming we take this on ourselves via the AJAX approach, determine API and server requirements if any.
• Document the feature as well as general philosophy (see wq/wq#10)

from wq.app.

The integration of redux-offline should help mitigate this (see #105).

from wq.app.