edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] interprocess messages
Date: Tue, 09 Dec 2014 03:06:59 -0800	[thread overview]
Message-ID: <87oardulnw.fsf@the-brannons.com> (raw)
In-Reply-To: <20141108142720.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 08 Dec 2014 14:27:20 -0500")

Karl Dahlke <eklhad@comcast.net> writes:

> As promised, here are some thoughts on messages between eb and the back-end

This looks like a very solid start to me.

I assume that for convenience, you'll be calling these two processes eb
and js, so I use those names below.

I noticed that there's not a corresponding "destroy object" message, but
the main eb process never really needs to be able to do that, does it?
On the other hand, the js process might very well destroy objects that
are known to the eb process, so we need some kind of message that can be
sent from js to eb:
object_was_destroyed, with parameters of a context number and object
number.

-- Chris

  parent reply	other threads:[~2014-12-09 11:08 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
2014-12-09 11:06 ` Chris Brannon [this message]
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=87oardulnw.fsf@the-brannons.com \
    --to=chris@the-brannons.com \
    --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).