Changes between Initial Version and Version 1 of Ticket #7544, comment 4


Ignore:
Timestamp:
May 22, 2011 10:42:21 AM (8 years ago)
Author:
wretched_dutchman
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7544, comment 4

    initial v1  
    1 I see multiple options in how to resolve this. Since google only supports 10 logins simultaneously we need to honor that.
    2 1) check how many simultaneous connections are possible and save this setting (and repeat this test once in a while). This can be done to test if the login is correct. Then open one socket per directory without starting the syncing-process. Now you can test which sockets do still allow a login and which don't (e.g. count how many login's are allowed simultaneous.) And of course while syncing with multiple connections also catch the failed to login-alert and see that the max connections is decreased.
    3 2) Allow the user to determine it's own maximum simultaneous connections in a setting (used by most clients as far as I'm aware of).
     1I see multiple options in how to resolve this. Since google only supports 10 logins simultaneously we need to honor that.[[BR]]
     21) check how many simultaneous connections are possible and save this setting (and repeat this test once in a while). This can be done to test if the login is correct. Then open one socket per directory without starting the syncing-process. Now you can test which sockets do still allow a login and which don't (e.g. count how many login's are allowed simultaneous.) And of course while syncing with multiple connections also catch the failed to login-alert and see that the max connections is decreased.[[BR]]
     32) Allow the user to determine it's own maximum simultaneous connections in a setting (used by most clients as far as I'm aware of).[[BR]]
    443) Use one connection in total, or do a serial retrieval of the directories which all it's own connection. This is the slowest option, but makes sure that you never exceed the limit of simultaneous connections.