cloud connection timeout

[Dirk Hohndel]

On Wed, Mar 23, 2016 at 10:22:40AM +0100, Thomas Pfeiffer wrote:
> On Dienstag, 22. März 2016 21:34:30 CET Dirk Hohndel wrote:
> > So in all honesty - I'm not sure what the right answer is here. I don't
> > think that a "several minutes" sync time is useful at all. That's why we
> > have the local cache. The problem is... how do we get people to do the
> > first sync where they have decent bandwidth and not on a trip...
> 
> Might it be possible to calculate the transfer volume beforehand and if it 
> exceeds a certain size and there is no (W)LAN connection, display a hint that 
> it would be better to sync on a broadband connection as it might take several 
> minutes with the current connection, with the option to override it?

Yes, git gives us a very vague idea of how big the transfer might be, but
that's long after the SSL connection was established. And Miika never gets
that far because we have a fairly short timeout for the SSL connection.

The problem is that we try to "quickly" figure out if we can get to the
cloud server or not. So we try to create an https connection to a certain
URL and check for the expected response. And if we don't get this
response, we decide that the connection is down.

/D