aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorThomas Harning Jr <harningt@gmail.com>2007-06-11 02:14:55 +0000
committerThomas Harning Jr <harningt@gmail.com>2007-06-11 02:14:55 +0000
commit320899f5436b5f0ea9eb0dca8af2bd9ec45e7c99 (patch)
tree8aca2e109a7655f921ca5dc37d49436184a12f90
parentb6f5c3902fea0e632439176349012d4d049f8837 (diff)
downloadluaevent-prosody-320899f5436b5f0ea9eb0dca8af2bd9ec45e7c99.tar.gz
luaevent-prosody-320899f5436b5f0ea9eb0dca8af2bd9ec45e7c99.zip
Added changelog
-rw-r--r--luaevent/CHANGELOG19
1 files changed, 19 insertions, 0 deletions
diff --git a/luaevent/CHANGELOG b/luaevent/CHANGELOG
new file mode 100644
index 0000000..58a4931
--- /dev/null
+++ b/luaevent/CHANGELOG
@@ -0,0 +1,19 @@
+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