Re: [Libevent-users] About the parameter of callback

2011-01-28 Thread ZHOU Xiaobo
I mean the error 'epoll'(or sth else) detected. for example, if a socket is closed by its peer, and the corresponding callback is invoked, how can the callback know that there is and error happened? try to read/write the socket first? - Original Message - From: "ren yufei" To: libevent-u

Re: [Libevent-users] About the parameter of callback

2011-01-28 Thread ren yufei
What kind of error on the socket did you refer? Because there is no 'EV_ERROR', you could not set this kind of event for detecting(as select). So, you don't have method or don't need detect ERR(please distinguish with err generated by read()) on a socket. Yufei _

[Libevent-users] About the parameter of callback

2011-01-28 Thread 守望者一号
The callback's prototype is (void)(*)(int, short, void*) the second parameter indicates what kind of event(s) happen. I found libevent-1.4.10 didn't have EV_ERROR. So my question is: When monitoring a socket, what value will be set to the second parameter if an error occurred on the socket? th

[Libevent-users] gevent 0.13.2 released

2011-01-28 Thread Denis Bilenko
Hi! I'm happy to announce that Gevent 0.13.2 is released with a number of bug fixes and a new gevent.httplib module that implements fast HTTP client - wrapper around libevent-http. What is it? gevent is a coroutine-based Python networking library that uses greenlet to provide a high-level synchr