luaevent/CHANGELOG

Wed, 13 Jun 2007 04:32:12 +0000

author
Thomas Harning Jr <harningt@gmail.com>
date
Wed, 13 Jun 2007 04:32:12 +0000
changeset 10
88ce07d62597
parent 6
59287edf821b
child 11
8339f6236a3c
permissions
-rw-r--r--

Setup management of socket create/close.
Recognized new bug: cannot create threads within threads... C contains reference to closed thread, not
global.

======
0.1.1 - Revision 14 - 2007-06-13
+ Fixed event-handling code to cancel events on nothing being returned
+ Added socket/object cleanup.
+ Filed bug to libevent about the strange valgrind-released errors
- Recognized following issues:
  Timeouts needed
  Need to handle events setup from inside a coroutine... need to get a global Lua state from a thread...
======
0.1.0 - Revision 6 - 2007-06-10 22:00 EST
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.
* Added cheap protection code for failures in callback handlers
======
0.0.0 - Revision 2 - 2007-06-10 12:00 EST
Initial public version, was broken due to self-resume coroutines

mercurial