with
it. :-)
--
Matthew Weigel
hacker
unique idempot.ent
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
evdns or evhttp?
--
Matthew Weigel
hacker
unique idempot . ent
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
of evhttp...
--
Matthew Weigel
hacker
unique idempot.ent
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
, and let the worker threads pull the structure back out of the
queue and use it to service the request.
--
Matthew Weigel
hacker
unique idempot.ent
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent
is not
the bottleneck. :-)
--
Matthew Weigel
hacker
unique idempot.ent
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users
Niels Provos wrote:
On Thu, Dec 4, 2008 at 2:15 PM, Matthew Weigel [EMAIL PROTECTED] wrote:
I'm still digging around in here, if I find much more to add I'll probably
submit a documentation patch.
EV_READ, EV_WRITE are mutually exclusive with EV_SIGNAL.
The confusion arises from everything
that triggered
the event and the type of event which will be either EV_TIMEOUT,
EV_SIGNAL, EV_READ, or EV_WRITE.
I'm still digging around in here, if I find much more to add I'll
probably submit a documentation patch.
--
Matthew Weigel
hacker
unique idempot . ent
describe, you'll still get errors for the event_test, signal_test, and
time_test subprojects.
Let me know if you have any more trouble.
--
Matthew Weigel
hacker
unique idempot.ent
___
Libevent-users mailing list
Libevent-users@monkey.org
http
).
My main goal was to get the regress project to build and run its
tests... I didn't pursue it past that.
--
Matthew Weigel
___
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users