From: "Roman Zhukov" <rzhukov@gmail.com>
To: fernanbolando@mailc.net,
"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] libevent for plan9
Date: Wed, 10 Dec 2008 10:12:23 +0500 [thread overview]
Message-ID: <881467ce0812092112o49e7e944q4244053bf5db645b@mail.gmail.com> (raw)
In-Reply-To: <1d5d51400812091928t68d33f7fxedfb0a91c385732b@mail.gmail.com>
You can just use blocking read/write calls in several threads.
On Wed, Dec 10, 2008 at 8:28 AM, Fernan Bolando <fernanbolando@mailc.net> wrote:
> Hi all
>
> I am looking into porting some stuff that uses libevent.
> http://monkey.org/~provos/libevent/
>
> I was wondering if there is something else I can use to replace
> libevent, so that I dont need to port it. Its probably to complex for
> me anyway.
>
> regards
> fernan
>
> --
> http://www.fernski.com
>
>
--
Roma
next prev parent reply other threads:[~2008-12-10 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 3:28 Fernan Bolando
2008-12-10 5:12 ` Roman Zhukov [this message]
2008-12-10 6:48 ` Roman Zhukov
2008-12-10 20:00 ` ron minnich
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=881467ce0812092112o49e7e944q4244053bf5db645b@mail.gmail.com \
--to=rzhukov@gmail.com \
--cc=9fans@9fans.net \
--cc=fernanbolando@mailc.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).