From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Romain Beauxis <toots@rastageeks.org>
Cc: caml-list@inria.fr,
"Savonet's developpers list" <savonet-devl@lists.sourceforge.net>
Subject: Re: [Caml-list] ocaml-duppy: an advanced scheduler for ocaml.
Date: Mon, 10 Mar 2008 19:57:00 +0100 [thread overview]
Message-ID: <1205175420.3991.6.camel@flake.lan.gerd-stolpmann.de> (raw)
In-Reply-To: <200803072208.09273.toots@rastageeks.org>
Am Freitag, den 07.03.2008, 22:08 +0100 schrieb Romain Beauxis:
> Le Friday 07 March 2008 21:58:26 Gerd Stolpmann, vous avez écrit :
> > How is that different from my equeue approach?
>
> Well, it is very similar, clearly.
> The difference I can see for now, is that Duppy is more simple and oriented
> toward socket events and delays. In particular, it is not clear to me wether
> equeue can accept delayed tasks.
>
> Of course, we didn't meant to deprecate your work, but perhaps it can be
> usefull for different taks..
My question was only out of curiosity. I am sometimes interested why
people reinvent wheels - and if it is only for a different color.
Equeue supports delays. It doesn't support priorities, however. Also,
multi-threading integration seems to be different.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
Phone: +49-6151-153855 Fax: +49-6151-997714
------------------------------------------------------------
prev parent reply other threads:[~2008-03-10 18:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 20:29 Romain Beauxis
2008-03-07 20:58 ` [Caml-list] " Gerd Stolpmann
2008-03-07 21:08 ` Romain Beauxis
2008-03-10 18:57 ` Gerd Stolpmann [this message]
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=1205175420.3991.6.camel@flake.lan.gerd-stolpmann.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=savonet-devl@lists.sourceforge.net \
--cc=toots@rastageeks.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 NNTP newsgroup(s).