Browse thread
async networking
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2006-02-07 (20:51) |
From: | Remi Vanicat <remi.vanicat@g...> |
Subject: | Re: [Caml-list] Re: async networking |
2006/2/7, Bardur Arantsson <spam@scientician.net>: > Gerd Stolpmann wrote: > > Yes, the default Equeue implementation bases simply on select(). It is, > > however, possible to develop alternate implementations. Currently, there > > are three of them which integrate into the event loops of labltk, > > lablgtk1 and lablgtk2. One could, for example, easily add an > > implementation for advanced kernel interfaces like epoll. > > Actually, it might be quite interesting to see one based on > poll()/epoll(), but I suspect it wouldn't matter much compared to all > the other stuff that's going in the Equeue code. This is just a very > vague hunch, though. I believe that labgtk (and so equeue over lablgtk) use poll. Note that you are adding another layer : glib, so you might not have gain a lot.