edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] JS1
Date: Mon, 24 Jul 2017 17:57:51 +0000	[thread overview]
Message-ID: <20170724175751.GC20415@odin> (raw)
In-Reply-To: <20170622224940.eklhad@comcast.net>

On Sat, Jul 22, 2017 at 10:49:40PM -0400, Karl Dahlke wrote:
> This is either for fun, or for testing, or for the future. I'm not sure.
> 
> export JS1=on

Ok, so how're we going to do all the async js stuff we'll have to start doing
properly soon?  Tbh I'm not sure how much I'm attached to the multiple process
idea other than it means js can go pop and we don't... but we *need* to sort
out async js soon.  Unfortunately websites are becoming increasingly reliant on
ajax being genuinely async and that's before we get to websockets etc.
With 2 processes it means that we can start with a simple interface with pipes
and select as now.  With 1 we'll need to do thread-safe programming to make this
fly properly.  It's not impossible but we'll have to make a bunch of changes to
make the existing code properly thread-safe to make that work, or have some way
to run duktape in a mode where it only does a certain amount of instructions and
use select/poll/some event loop to allow io, comms and js to work together...
Honestly I'm not sure what the right design is yet. I've been, unfortunately,
rather busy and unable to do much on edbrowse recently so I'm still catching up
with things.
That being said, this variable, plus the fact that we've made the switch to
duktape (well done for that, sorry I ran out of time to help) gives us a
mechanism to may be play with some sort of different model for running js.

Cheers,
Adam.

  reply	other threads:[~2017-07-24 17:57 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 [this message]
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
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=20170724175751.GC20415@odin \
    --to=arthompson1990@gmail.com \
    --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).