hail-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: Reconsidering libevent
Date: Tue, 21 Sep 2010 17:54:02 -0400	[thread overview]
Message-ID: <AANLkTi=c=smLZCVJew3tHOfsArqiuOyR5c5yHvN3M5PS@mail.gmail.com> (raw)
In-Reply-To: <20100921154158.1bab5239@lembas.zaitcev.lan>

On Tue, Sep 21, 2010 at 5:41 PM, Pete Zaitcev <zaitcev@redhat.com> wrote:
> Back in the day I spent some effort divorcing libhail and libevent.
> With some thinking it should be possible for tcp_write_* as well.

tcp_write_* could call ->{ev_set,ev_add,ev_del} callbacks just as
easily as direct libevent calls...

      reply	other threads:[~2010-09-21 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 20:51 Reconsidering libevent Jeff Garzik
2010-09-21 21:06 ` Steven Dake
2010-09-21 21:09   ` Jeff Garzik
2010-09-21 21:41 ` Pete Zaitcev
2010-09-21 21:54   ` Jeff Garzik [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='AANLkTi=c=smLZCVJew3tHOfsArqiuOyR5c5yHvN3M5PS@mail.gmail.com' \
    --to=jeff@garzik.org \
    --cc=hail-devel@vger.kernel.org \
    --cc=zaitcev@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).