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] Threads (fwd)
Date: Wed, 28 Aug 2019 02:25:59 -0400	[thread overview]
Message-ID: <20190728022559.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1908272234510.15625@phoenix>

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

The xhr system is necessarily sequential, as far as I can tell.
Javascript rolls along and decides it needs some data, and asks for it by xhr, and stops, and waits, and really can't do anything else until that data is returned.
There isn't any point to putting that download into a background thread, you still have to wait for it, so no, threading won't speed up any xhr requests.
And this is almost always dynamic data so not cacheable.

I guess a test might be a site with lots of js, like nasa, without any caching, and with or without jsbg.
Even if it doesn't speed things up a lot I'm glad I did it, for several reasons.

Karl Dahlke

  reply	other threads:[~2019-08-28  6:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  5:46 Kevin Carhart
2019-08-28  6:25 ` Karl Dahlke [this message]
2019-08-29  3:23   ` Kevin Carhart
2019-08-29 19:46   ` Geoff McLane
2019-08-29 21:05     ` Karl Dahlke
2019-08-30 19:23       ` Geoff McLane
2019-08-30 21:26         ` Karl Dahlke
2019-08-30 22:08         ` Karl Dahlke
2019-08-31 19:05           ` Geoff McLane
2019-09-01  2:58 Kevin Carhart
2019-09-01  3:04 ` Karl Dahlke
2019-09-01 18:37   ` Geoff McLane
2019-09-02  2:48     ` Karl Dahlke
2019-09-02 18:38       ` Geoff McLane
2019-09-02 18:53         ` Karl Dahlke

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=20190728022559.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).