TODO: figure out why server is not honoring the minimum scan period configuration
...
1. Purposeful termination of connection dialog no longer prompts for retry confirmation
2. Can now specify client side on connection attempt the ideal refresh period
3. TODO: Client side needs to enforce the synchronicity delay (probably just use a self adding task to the screen fetching dispatcher that sleeps for the delay)
Clients now obey their own throttle setting for syncing with the server
Server now syncs as fast as fastest client wants, but not faster than a global value
So it appears as if each client has it's own polling mechanism when they all actually share ONE mechanism
minor fix
Merge pull request #9 from josephcopenhaver/feature/flexible-frequencies

Feature/flexible frequencies