This is Part 3 of a four part series where we explore some of the tools available to detect and manage online/offline connectivity in web/mobile applications. In Part 1 we looked at the available APIs for detecting connectivity state (and the woes associated with them). In Part 2 we wrote a hand-rolled abstraction to manage using these APIs together and began to see elements of a state machine emerge from the chaos. In this post we're going to drive the state machine stake deeper by exploring how we can keep our FSMs from violating SRP, and set the stage for using multiple FSMs together to model more complex application behavior.
By submitting this form, you understand and agree that your personal data will be processed by Progress Software or its Partners as described in our Privacy Policy. You may opt out from marketing communication at any time here or through the opt out option placed in the e-mail communication sent by us or our Partners.
We see that you have already chosen to receive marketing materials from us. If you wish to change this at any time you may do so by clicking here.
Thank you for your continued interest in Progress. Based on either your previous activity on our websites or our ongoing relationship, we will keep you updated on our products, solutions, services, company news and events. If you decide that you want to be removed from our mailing lists at any time, you can change your contact preferences by clicking here.