You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2021. It is now read-only.
It would be good to do some kind of verification (e.g. checksum) on our web app code, maybe as a tool in the demo app, or maybe as an automatic check on startup (better) (which may or may not be technically possible) .
Wireless networks can be very unreliable and lead to incomplete sync sessions or corrupt data.
One one particular network (Highland Capital office wifi in London) I observed inconsistent network behaviour and this was correlated with various breakage modes of the Bootcards demo app, whether it was the stable release or the new release. So it seems that you can break a web app, especially when it is working in full screen mode, just by downloading and installing it over an unreliable network (by unreliable, I mean a network that is prone to random and significant packet loss).
(btw I've seen this sort of behaviour before in Unplugged, with the Unplugged Android engine, which uses an older version of the Unplugged sync code which has less error checking in the sync protocol compared to the latest iOS release. It's very disconcerting when it happens, because it causes you to lose trust in the app)
The text was updated successfully, but these errors were encountered:
It would be good to do some kind of verification (e.g. checksum) on our web app code, maybe as a tool in the demo app, or maybe as an automatic check on startup (better) (which may or may not be technically possible) .
Wireless networks can be very unreliable and lead to incomplete sync sessions or corrupt data.
One one particular network (Highland Capital office wifi in London) I observed inconsistent network behaviour and this was correlated with various breakage modes of the Bootcards demo app, whether it was the stable release or the new release. So it seems that you can break a web app, especially when it is working in full screen mode, just by downloading and installing it over an unreliable network (by unreliable, I mean a network that is prone to random and significant packet loss).
(btw I've seen this sort of behaviour before in Unplugged, with the Unplugged Android engine, which uses an older version of the Unplugged sync code which has less error checking in the sync protocol compared to the latest iOS release. It's very disconcerting when it happens, because it causes you to lose trust in the app)
The text was updated successfully, but these errors were encountered: