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] branch proc1
Date: Sat, 12 Aug 2017 05:02:46 -0400	[thread overview]
Message-ID: <20170712050246.eklhad@comcast.net> (raw)

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

I would like to make the connection between our html tags and the js objects considerably more efficient,
so when duktape frees an object we quickly manage the corresponding tag.
Right now there are linear searches through every frame in every window on edbrowse, and other such ugliness.
This is part of the reason edbrowse is slow.
A better connection almost demands one process.
Almost, I know how to do it with 2, but it's a lot more work, along a path that I'm pretty sure is a dead end, and I really don't want to bother with that.
So I propose a new branch, proc1, wherein I am committed to one process, and can realize all the efficiency gains therein, and remove the messaging code for 2 processes
and passing curl space information back and forth and all that.
You might want to follow this branch to help me test and debug.
If and when we're all comfortable with it we can merge back to master, just as we did with duktape.
And like duktape, it will be a decision that is very hard to undo, so we definitely want to feel good about it.
We want to feel like js hardly ever seg faults, for instance.
I already feel pretty good about interrupting js with ^c in a graceful manner; that seems to work.
So keep an eye out for branch proc1, and follow along.

Karl Dahlke

                 reply	other threads:[~2017-08-12  9:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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