While this is all theoretical and tangential (I¹m guessing the behavior is a
bug and not a design feature), I¹ll stand by original comment. I feel if
you¹re going to go to the added complexity of doing event driven I/O you
probably have a complex enough app that you want to use threads at the same
time. Maybe you want to avoid blocking disk I/O or maybe you want to take
advantage of a multiple execution cores. Things like that.

Chris

On 5/16/08 6:15 PM, "Dan Fandrich" <dan_at_coneharvesters.com> wrote:

> On Fri, May 16, 2008 at 05:36:54PM -0700, Christopher Palow wrote:
>> > I actually don't have a threaded program so I'm turning signals back on
>> now,
>> > but I figure most people using the multi interface also use threads.
>
> I would guess the opposite--the multi interface gives single threaded
> programs a way to perform concurrent transfers. Multithreaded programs can
> just use the easy interface in each thread.
>
>>>> >>> Dan
> --
> http://www.MoveAnnouncer.com The web change of address service
> Let webmasters know that your web site has moved
>
Received on 2008-05-17