changelog
- Wed, 13 Jun 2007 03:29:11 +0000
- by Thomas Harning Jr <harningt@gmail.com> [Wed, 13 Jun 2007 03:29:11 +0000] rev 8
- Performed some refactoring...
- Wed, 13 Jun 2007 02:13:18 +0000
- by Thomas Harning Jr <harningt@gmail.com> [Wed, 13 Jun 2007 02:13:18 +0000] rev 7
- Fixed the strange event error... it was adding events to a dead socket.
- Mon, 11 Jun 2007 02:17:23 +0000
- by Thomas Harning Jr <harningt@gmail.com> [Mon, 11 Jun 2007 02:17:23 +0000] rev 6
- Reformatted changlog
- Mon, 11 Jun 2007 02:14:55 +0000
- by Thomas Harning Jr <harningt@gmail.com> [Mon, 11 Jun 2007 02:14:55 +0000] rev 5
- Added changelog
- Mon, 11 Jun 2007 01:52:16 +0000
- by Thomas Harning Jr <harningt@gmail.com> [Mon, 11 Jun 2007 01:52:16 +0000] rev 4
- Fixed stack overflow issue. (Forgot to pop error/integer)
- Mon, 11 Jun 2007 01:24:10 +0000
- by Thomas Harning Jr <harningt@gmail.com> [Mon, 11 Jun 2007 01:24:10 +0000] rev 3
- * Added some cheap protection code for failures in callback
functions.
- Mon, 11 Jun 2007 01:08:59 +0000
- by Thomas Harning Jr <harningt@gmail.com> [Mon, 11 Jun 2007 01:08:59 +0000] rev 2
- * Completed mostly working version
* Moved to a mode where addevent calls a callback rather than
it being instantiated within.
* If the callback returns -1, then no event is ever setup
* Otherwise the integer value is used to setup the event
* This allows for using coroutine.wrap rather than a cooked-up wrapper
* Tests work, although there are a few remaining issues:
* Need to figure a good way of preserving the event object,
not sure if current method is good enough, since the socket
is the only anchor, and it is only held inside the coro..
circular reference, something that Lua 'handles' well.
* Doing more than the maximum sockets the process is allows
causes strangeness to occur in libevent.. somehow
it is getting around to epoll_add which is causing valgrind
to barf.
