edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]   Short Timers
Date: Sat, 11 Apr 2015 10:44:58 -0400	[thread overview]
Message-ID: <20150311104458.eklhad@comcast.net> (raw)

There is another problem with my quick&dirty approach,
running the short timers now and then returning control to the user.
A timer that fires in 5 milliseconds,
that I decide to run now, may well queue up another timer that fires in 5 ms.
Well my software might figure: it's just 5 ms away, run it now.
It queues up another timer in 5 ms, which I run, and so on,
and suddenly I'm in an infinite loop and the user is locked out.
Of course in any other browser this does something 100 times a second,
in the background, without churning the cpu, and without locking
out the user.
So whatever we decide, it has to be a bit smarter than just:
run the shor ttimers now and put the long timers under user synchronous control.
Perhaps Adam's background model or some other model.
Anyways I'm not going to mess with these for a while,
until we can all give it a bit more thought.

Karl Dahlke

             reply	other threads:[~2015-04-11 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 14:44 Karl Dahlke [this message]
2015-04-11 15:23 ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2015-04-11  3:48 Karl Dahlke
2015-04-11 14:11 ` Adam Thompson
2015-04-11 14:46   ` Chris Brannon
2015-04-11 15:18     ` Adam Thompson
2015-04-08 13:19 Karl Dahlke
2015-04-10 11:28 ` Adam Thompson
2015-04-11  1:39   ` Chris Brannon

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=20150311104458.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).