| To: | "Viner, David" <dviner@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: fam vs libevent? |
| From: | Michael Raymond <mraymond@xxxxxxx> |
| Date: | Thu, 23 Oct 2003 14:01:49 -0500 |
| Cc: | "'fam@xxxxxxxxxxx'" <fam@xxxxxxxxxxx> |
| In-reply-to: | <263A1F717ECDED40AA969F98D1CF122E0F7B01@xxxxxxxxxxxxxxxxxxxxx>; from dviner@xxxxxxxxxxxxx on Thu, Oct 23, 2003 at 11:08:18AM -0700 |
| References: | <263A1F717ECDED40AA969F98D1CF122E0F7B01@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | fam-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
Different OS's support different versions of /dev/poll, kqueue,
/dev/epoll, etc. libevent exists to allow an application program to a
single interface and let the library worry about working with what the OS
supports. FAM isn't so much interested in socket events for network servers
as it is targeted at events in normal files in the filesytem. That's my
experience at least.
Michael
On Thu, Oct 23, 2003 at 11:08:18AM -0700, Viner, David wrote:
> can someone with more knowledge than i explain the differentiating features
> of FAM and libevent? both seem to address the same problem area. libevent
> information can be found at http://www.monkey.org/~provos/libevent/
>
> thanks
> dave
>
>
--
Michael A. Raymond
Core OS Scheduling Group Real-Time Lead
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | fam vs libevent?, Viner, David |
|---|---|
| Next by Date: | Re: fam vs libevent?, Steven W. Orr |
| Previous by Thread: | fam vs libevent?, Viner, David |
| Next by Thread: | Re: fam vs libevent?, Steven W. Orr |
| Indexes: | [Date] [Thread] [Top] [All Lists] |