Skip to content

Page Event Scenarios

Jump to bottom Edit New page
Colin Law edited this page Nov 5, 2017 · 7 revisions

Use this page to document the different possible page events in order (the control msgs). This will be used to work out the best approach for cache replays. Entries with an * come from the client, everything else comes from the server.

New Client page

'server connected', 'ready for content'*

CDL: but note that these could (I think) occur in either order.

Client page closed (e.g. tab/window closed)

'server disconnected'

Client page reload

'server disconnected', 'server connected', 'ready for content'*

Socket dropped and reconnected

'server disconnected', 'server connected'*

CDL: (Edited) To replicate this (on my Android phone at least, don't know about others) open the page and switch away from it. Leave it for 10 minutes or so till the socket disconnected message appears, then re-open it on the phone. This generates the connected message but no page reload. This is why we had to put in the repeating re-connect attempts as sometimes it did not re-connect automatically - see issue #9

Please feel free to add comments to the page (clearly mark with your initials & please add a commit msg so we know what has changed). You can contact me in the Discourse forum, or raise an issue here in GitHub! I will make sure all comments & suggestions are represented here.

Clone this wiki locally