unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Chaos Eternal <chaoseternal@shlug.org>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: asynchronous socket library
Date: Tue, 16 Jul 2013 15:36:48 +0800	[thread overview]
Message-ID: <CAGyY8Nuq-=hK2AkU3vFoeosNSZY06SSTH47-twd=fXWXKsoQWA@mail.gmail.com> (raw)
In-Reply-To: <CA+XASoVJCi2+nPMe=o-QKYos4cUE1wi9iGmXq5dv7fNH=S9kQw@mail.gmail.com>

i think there is a nio branch for guile?
nio means non-blocking io

On Tue, Jul 16, 2013 at 3:02 PM, Aleix Conchillo Flaqué
<aconchillo@gmail.com> wrote:
> On Mon, Jul 15, 2013 at 11:15 PM, Javier Sancho <jsf@jsancho.org> wrote:
>> Aleix Conchillo Flaqué wrote:
>>> I was wondering if there is (or someone is working on) an asynchronous
>>> socket library for Guile. I was thinking in a pure scheme library (not
>>> bindings for libevent or some other).
>>
>> If you don't use libevent, at least you'll need poll, epoll or
>> something similar. Or how are you planning to monitor activity on a
>> file descriptor?
>>
>
> My idea was to create something simple on top of system calls, as
> libevent does. This might mean that I need additional system calls
> that are not in guile yet. But it doesn't mean I need to create
> bindings for libevent (which would probably be smarter if I wanted
> something complete). Basilica, the main idea is to learn in the
> process.
>
> Aleix
>



  parent reply	other threads:[~2013-07-16  7:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 23:41 asynchronous socket library Aleix Conchillo Flaqué
2013-07-16  1:03 ` Nala Ginrut
2013-07-16  1:42   ` Aleix Conchillo Flaqué
2013-07-16  6:15 ` Javier Sancho
2013-07-16  7:02   ` Aleix Conchillo Flaqué
2013-07-16  7:03     ` Aleix Conchillo Flaqué
2013-07-16  7:36     ` Chaos Eternal [this message]
2013-07-16 15:24       ` Aleix Conchillo Flaqué
2013-07-16 15:58         ` Chaos Eternal
2013-07-16 17:02           ` Aleix Conchillo Flaqué
2013-07-16  7:50     ` Thien-Thi Nguyen
2013-07-16 15:26       ` Aleix Conchillo Flaqué
2013-07-17  6:07 ` mark
2013-07-17  7:13   ` Mark H Weaver
2013-07-17 16:49     ` mark
2013-08-24 21:33       ` Mark H Weaver
2013-08-25 22:26         ` mark.d.witmer

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='CAGyY8Nuq-=hK2AkU3vFoeosNSZY06SSTH47-twd=fXWXKsoQWA@mail.gmail.com' \
    --to=chaoseternal@shlug.org \
    --cc=aconchillo@gmail.com \
    --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).