From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) by hurricane.the-brannons.com (Postfix) with ESMTPS id C297877AA1 for ; Tue, 27 Aug 2019 23:26:03 -0700 (PDT) Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id 2rP6ieNidxbjx2rP6iXn0z; Wed, 28 Aug 2019 06:26:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1566973560; bh=MpeVjomV8ibnS6jghuIgoF/TJawDSgdsoH1obauB/SM=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=koAbZTVYWuOzS4COhxYP7kDwIeeMwiH/jt+5XTpgzQwWVfiJqfQ2kLhTAVfiq9TuJ VMZI9uX4n8q77INLZWFva7XhTULe7VZt8vsqL14qFqZXRZp2gaqBmF21sOByOqP291 /fFXfWFoErL/gQyvHl09qkVJ7ufbSNvspKjZgxEh5fKl3cJk5FmxamOmHETloVE/2a kc2Tfst8QsHqkdh1klqD2KkNifWdl61crUXnvrIFGjWl5LalGDHdYHp7yWW8EOMgAh YAO0IE3Q92gZDguMYVsaNkwsModFzQ+HbTfzi6YlQpT1BfcsJNcou8shVqUh2bXYWM LFj8NIVqHYziw== Received: from unknown ([IPv6:2601:408:c303:3f49:21e:4fff:fec2:a0f1]) by resomta-ch2-20v.sys.comcast.net with ESMTPSA id 2rP5i1G72s8qC2rP6iTnVY; Wed, 28 Aug 2019 06:26:00 +0000 X-Xfinity-VMeta: sc=0;st=legit To:Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E) Subject: [edbrowse-dev] Threads (fwd) Date: Wed, 28 Aug 2019 02:25:59 -0400 Message-ID: <20190728022559.eklhad@comcast.net> X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=nextpart-eb-606625 Content-Transfer-Encoding: 7bit This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --nextpart-eb-606625 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 --nextpart-eb-606625--