From: Chris Vine <chris@cvine.freeserve.co.uk>
To: Guile User <guile-user@gnu.org>
Subject: Re: Potluck - thread safe event loop with await semantics
Date: Mon, 22 Feb 2016 18:12:38 +0000 [thread overview]
Message-ID: <20160222181238.44241ad8@dell.homenet> (raw)
In-Reply-To: <CAJ=RwfaQmR_AWW1uDuRtcY23qFb0KkMAtOuM_XscC9TPACxoKg@mail.gmail.com>
On Mon, 22 Feb 2016 12:53:10 -0500
"Thompson, David" <dthompson2@worcester.edu> wrote:
> On Mon, Feb 22, 2016 at 12:40 PM, Chris Vine
> <chris@cvine.freeserve.co.uk> wrote:
>
> > The other thing that may require further work is the
> > documentation. I am used to doxygen or gtk-doc, neither of which I
> > imagine will parse guile scheme code, so I will have to look into
> > what is available (I don't like info).
> >
> > I'll post the URL when I have put it up.
>
> Please consider unifying with Chris Webber's 8sync project, which
> covers the same territory and has been approved as an official GNU
> project.
>
> https://notabug.org/cwebber/8sync
8sync has a nice design but the two cannot be unified because (i) 8sync
does not try to be thread safe (it is strictly single-threaded), and
(ii) it does not wrap an external event loop such as the glib/gtk+
event loop. In a number of ways it is considerably more sophisticated
than my code, because it does not reveal the event loop at all, nor for
that matter does it explicitly reveal its await/resume continuations.
It is highly abstracted.
They are just different things, which happen to both use delimited
continuations in the same way. In particular, I think it essential
that an asynchronous event loop should have the ability for worker
threads to post events to it.
Chris
next prev parent reply other threads:[~2016-02-22 18:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 21:45 Potluck - thread safe event loop with await semantics Chris Vine
2016-02-22 12:01 ` Ludovic Courtès
2016-02-22 16:36 ` Marko Rauhamaa
2016-02-22 17:40 ` Chris Vine
2016-02-22 17:53 ` Thompson, David
2016-02-22 18:12 ` Chris Vine [this message]
2016-02-22 19:54 ` Christopher Allan Webber
2016-02-22 20:28 ` David Pirotte
2016-02-23 0:31 ` Chris Vine
2016-02-23 1:30 ` Chris Vine
2016-02-23 19:55 ` David Pirotte
2016-02-23 6:25 ` David Pirotte
2016-02-23 12:09 ` Chris Vine
2016-02-23 16:49 ` Chris Vine
2016-02-25 23:22 ` David Pirotte
2016-02-23 4:58 ` Chris Vine
2016-03-01 20:39 ` Amirouche Boubekki
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160222181238.44241ad8@dell.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).