2 0.1.1 - Revision 14 - 2007-06-13
3 + Fixed event-handling code to cancel events on nothing being returned
4 + Added socket/object cleanup.
5 + Filed bug to libevent about the strange valgrind-released errors
6 - Recognized following issues:
8 Need to handle events setup from inside a coroutine... need to get a global Lua state from a thread...
10 0.1.0 - Revision 6 - 2007-06-10 22:00 EST
11 Completed mostly working version
12 * Moved to a mode where addevent calls a callback rather than it being instantiated within.
13 If the callback returns -1, then no event is ever setup,
14 Otherwise the integer value is used to setup the event.
15 This allows for using coroutine.wrap rather than a cooked-up wrapper
16 * Tests work, although there are a few remaining issues:
17 * Need to figure a good way of preserving the event object,
18 not sure if current method is good enough, since the socket
19 is the only anchor, and it is only held inside the coro..
20 circular reference, something that Lua 'handles' well.
21 * Doing more than the maximum sockets the process is allows
22 causes strangeness to occur in libevent.. somehow
23 it is getting around to epoll_add which is causing valgrind
25 * Added cheap protection code for failures in callback handlers
27 0.0.0 - Revision 2 - 2007-06-10 12:00 EST
28 Initial public version, was broken due to self-resume coroutines