edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] JS1
Date: Sat, 12 Aug 2017 00:20:27 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1708112337080.25964@carhart.net> (raw)
In-Reply-To: <20170711055110.eklhad@comcast.net>



> Is there really a site that *needs* timers faster than 500ms for nonvisual purposes?
> Kevin you've combed through the acid tests, is this a concern?

Hmmm.... I'm in the file right now and I'm searching 'imeout' to try to
find instances of setTimeout and 'nterval' to try to find instances of 
setInterval.

setInterval doesn't appear at all.

setTimeout appears only twice.  In both cases, it's called like this:
             setTimeout(update, delay);

So what values does the variable 'delay' hold?  It's set to 10 higher up.

   var delay = 10;

However, there is also this reference to 5000ms in a comment:

           // we will give this test 500 attempts (5000ms) before aborting

So based on what value they hardcoded, maybe you could conclude from this 
that the scale along which they are mapping the range from good 
responsiveness to poor responsiveness is measured in seconds and not 
tenths of a second?  If that is right, I think the answer to your question 
is probably no and 500ms is faster than the values they used most of the 
time.  500ms is only 50 attempts, when they're willing to give the client 
ten times as long as that to finish a test.

Kevin



  reply	other threads:[~2017-08-12  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-23  2:49 Karl Dahlke
2017-07-24 17:57 ` Adam Thompson
2017-07-28 17:39   ` Karl Dahlke
2017-07-28 19:51     ` Adam Thompson
2017-07-28 22:05       ` Karl Dahlke
2017-08-11  7:46         ` Adam Thompson
2017-08-11  9:51           ` Karl Dahlke
2017-08-12  7:20             ` Kevin Carhart [this message]
2017-08-12  7:30               ` Karl Dahlke
2017-08-12  8:06                 ` Kevin Carhart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.03.1708112337080.25964@carhart.net \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).