From: Eris Discordia <eris.discordia@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] critique of sockets API
Date: Fri, 12 Jun 2009 08:21:50 +0100 [thread overview]
Message-ID: <174A3DE4FB57AB50A9230C11@[192.168.1.2]> (raw)
In-Reply-To: <9ab217670906111634m735febcfsaac86e35e9a7d635@mail.gmail.com>
> s/could be/is/
>
> From real world product experience across multiple operating systems
> and architectures.
So there is at least one example to support the case for callbacks. I am
pretty convinced there are many more examples.
--On Thursday, June 11, 2009 19:34 -0400 "Devon H. O'Dell"
<devon.odell@gmail.com> wrote:
> 2009/6/11 Eris Discordia <eris.discordia@gmail.com>:
>>> but given that plan 9 is about having a system that's easy
>>> to understand and modify, i would think that it would be
>>> tough to demonstrate that asyncronous i/o or callbacks
>>> could make the system (or even applications) simplier.
>>> i doubt that they would make the system more efficient,
>>> either.
>>>
>>> do you have examples that demonstrate either?
>>
>> I can't claim I have anything in code which would be necessary for an
>> actual demonstration or for going beyond the "talk talk talk" stage. I
>> can, however, present one simple case: in some applications asynchronous
>> name resolving is a must and it can be realized by either of threads or
>> callbacks. Crawlers and scanners come to mind. Spawning threads for DNS
>> requests could be more costly than registering a set of callbacks within
>> one thread and then harvesting the results within that same thread.
>
> s/could be/is/
>
> From real world product experience across multiple operating systems
> and architectures.
>
next prev parent reply other threads:[~2009-06-12 7:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b0a72b5826eb44300d3603f585859910@quanstro.net>
2009-06-11 14:54 ` Eris Discordia
2009-06-11 18:24 ` erik quanstrom
2009-06-11 21:21 ` Eris Discordia
2009-06-11 23:41 ` erik quanstrom
2009-06-12 4:32 ` Paul Lalonde
2009-06-12 7:19 ` Eris Discordia
[not found] ` <D9FE8C51EE2D568C05E555DD@192.168.1.2>
2009-06-11 23:34 ` Devon H. O'Dell
2009-06-12 7:21 ` Eris Discordia [this message]
[not found] <mailman.1.1244808001.26495.9fans@9fans.net>
2009-06-13 1:39 ` Bhanu Nagendra Pisupati
2009-06-11 12:16 erik quanstrom
[not found] <mailman.1.1244635201.19660.9fans@9fans.net>
2009-06-10 23:46 ` Bhanu Nagendra Pisupati
[not found] <mailman.1007.1244590421.1513.9fans@9fans.net>
2009-06-10 22:50 ` Bhanu Nagendra Pisupati
2009-06-11 12:34 ` erik quanstrom
[not found] <mailman.998.1244574121.1513.9fans@9fans.net>
2009-06-09 23:20 ` Bhanu Nagendra Pisupati
2009-06-09 23:24 ` J.R. Mauro
2009-06-09 23:33 ` Devon H. O'Dell
2009-06-10 3:33 ` Gary Wright
2009-06-10 0:07 ` erik quanstrom
2009-06-10 0:34 ` erik quanstrom
2009-06-11 7:07 ` Eris Discordia
-- strict thread matches above, loose matches on Subject: below --
2009-06-09 18:49 Bhanu Nagendra Pisupati
2009-06-09 18:59 ` erik quanstrom
2009-06-09 22:11 ` Russ Cox
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='174A3DE4FB57AB50A9230C11@[192.168.1.2]' \
--to=eris.discordia@gmail.com \
--cc=9fans@9fans.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).