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] interprocess messages
Date: Tue, 9 Dec 2014 07:53:11 +0000	[thread overview]
Message-ID: <20141209075311.GQ14122@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20141108142720.eklhad@comcast.net>

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

On Mon, Dec 08, 2014 at 02:27:20PM -0500, Karl Dahlke wrote:
> As promised, here are some thoughts on messages between eb and the back-end
> js process.
> Please remember that this is intended as increment,
> and so there are messsages to do the things we do today,
> while other messages and functionality will come later.

Ok, how are you planning on implementing this in terms of ipc?
Pipes, sockets or message queues would be the three I'd think of here.
Also, with the aim of incrementing in the right direction,
how would this play with blocking calls,
and the ability to run js asynchronously?
If we're going to do this kind of redesign we need to look at this stuff or in
a few years edbrowse will be basically unusable on the internet due to the
(often ridiculous) amount of ajax and friends being used on modern websites.
The more I think about how this is going to work,
the more I think we need to look at dynamically managing the js heap and having
a js process per session (at least) in order to make things work on the modern internet.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-12-09  7:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 19:27 Karl Dahlke
2014-12-09  7:53 ` Adam Thompson [this message]
2014-12-09 11:06 ` Chris Brannon
2014-12-09 14:13 Karl Dahlke
2014-12-09 15:57 ` Chris Brannon
2014-12-09 23:01   ` Adam Thompson
2014-12-09 18:23 ` Adam Thompson

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=20141209075311.GQ14122@toaster.adamthompson.me.uk \
    --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).