From kde-usability  Tue May 31 09:31:52 2005
From: Thomas Zander <zander () kde ! org>
Date: Tue, 31 May 2005 09:31:52 +0000
To: kde-usability
Subject: Re: Splash screen while waiting for IMAP data to be fetched (Re:
Message-Id: <200505311131.53365.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-usability&m=111753199016883
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1502960607=="

--===============1502960607==
Content-Type: multipart/signed;
  boundary="nextPart2939600.2kLfoD7DfG";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2939600.2kLfoD7DfG
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 30 May 2005 21:53, Martijn Klingens wrote:
> If your server consistenly needs 0.5-0.7 seconds then I can understand
> your argument, but I wonder if you're the common case or the exception.
>
> Does anyone else have an opinion on the matter?

What about storing the time it took to actually update and if smaller then=
=20
1500msec make the timeout of the timer higher for a next refresh.
Making a int[10] with the last 10 timeouts (for remote servers) and=20
selecting the longest timeout, which is still smaller then 1500msec  should=
=20
do the trick.

=2D-=20
Thomas Zander

--nextPart2939600.2kLfoD7DfG
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCnC8JCojCW6H2z/QRAmJHAJ9QIJND9THTbHm699ongjfiPbRl0gCg5VGs
Yhj8VA4FK2dQXCsZuPbFc7M=
=ZQgV
-----END PGP SIGNATURE-----

--nextPart2939600.2kLfoD7DfG--

--===============1502960607==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

--===============1502960607==--