Page Event Scenarios

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

'client connect', 'ready for content'*

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

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

'client disconnect'

Client page reload

'client disconnect', 'client connect', 'ready for content'*

Socket dropped and reconnected

'client disconnect', 'client connect'

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

Application specific client generated events

These can happen at any time (presumably after 'ready for content') but in particular are likely to happen shortly after 'ready for content', for example when riot.js tags have been mounted.