| 1 | 0.3.2 - 2011-07-06 |
| 2 | * Fixed recorded version in Lua |
| 3 | 0.3.1 - 2011-01-15 |
| 4 | * Merged all of luaevent-prosody (0.1.1) changes (missed updates) |
| 5 | 0.3.0 - 2011-01-15 |
| 6 | * Fixed libevent 2.0 compilation errors |
| 7 | * Merged all of luaevent-prosody (0.1.0) changes |
| 8 | * Removes low-level read access to watermark & timeout values that break API |
| 9 | * Switches to watermark write accessor function to avoid API break |
| 10 | ====== |
| 11 | luaevent-prosody 0.1.1 - 2010-02-25 |
| 12 | * Fix overflow with high event timeouts |
| 13 | ====== |
| 14 | luaevent-prosody 0.1.0 - 2010-02-15 |
| 15 | * Fixed stack slot leak in event callbacks |
| 16 | * Fixed stack slot leak when error occurs in callback |
| 17 | * Various compilation fixes for Windows/ANSI C |
| 18 | * Silence some compiler warnings |
| 19 | + Add base:loopexit() method, with timeout support |
| 20 | + Add base:method() to discover backend in use |
| 21 | + Add core.libevent_version() to detect libevent version |
| 22 | + Add _NAME and _VERSION fields to module table |
| 23 | + base:addevent() now accepts integer fd to watch |
| 24 | + Switched from premake to standard Makefile for building |
| 25 | ====== |
| 26 | 0.2.0 - 2007-09-21 |
| 27 | + Reorganized project to better fit GIT |
| 28 | + Refactored and cleaned sources |
| 29 | * Broke event_callback into its own source file |
| 30 | + Added timer/timeout capabilities + minor test |
| 31 | + Added event_buffer object |
| 32 | * Can 'add' a sequence of strings/event_buffers |
| 33 | * Can 'get_data', 'length','drain','close' and create new instances |
| 34 | * Can 'readline', 'read' from file des, 'write' to file des |
| 35 | * Added lunit tests for basic functions (read/write from/to FD) |
| 36 | ====== |
| 37 | 0.1.2 - 2007-08-18 |
| 38 | + Setup system to use new coro management as described in COROUTINE_MANAGEMENT |
| 39 | The callbacks are called from the event_loop 'thread' rather than that which they are |
| 40 | created in. This will prevent the self-resume problem as well as dead-thread problems. |
| 41 | - Recognized issues to fix in next release: |
| 42 | * Socket/event closing needs to be cleaned |
| 43 | * luaevent.lua needs refactoring |
| 44 | * luaevent.[ch] need to be cleaned up |
| 45 | ====== |
| 46 | 0.1.1 - 2007-06-13 |
| 47 | + Fixed event-handling code to cancel events on nothing being returned |
| 48 | + Added socket/object cleanup. |
| 49 | + Filed bug to libevent about the strange valgrind-released errors |
| 50 | - Recognized following issues: |
| 51 | Timeouts needed |
| 52 | Need to handle events setup from inside a coroutine... need to get a global Lua state from a thread... |
| 53 | ====== |
| 54 | 0.1.0 - 2007-06-10 22:00 EST |
| 55 | Completed mostly working version |
| 56 | * Moved to a mode where addevent calls a callback rather than it being instantiated within. |
| 57 | If the callback returns -1, then no event is ever setup, |
| 58 | Otherwise the integer value is used to setup the event. |
| 59 | This allows for using coroutine.wrap rather than a cooked-up wrapper |
| 60 | * Tests work, although there are a few remaining issues: |
| 61 | * Need to figure a good way of preserving the event object, |
| 62 | not sure if current method is good enough, since the socket |
| 63 | is the only anchor, and it is only held inside the coro.. |
| 64 | circular reference, something that Lua 'handles' well. |
| 65 | * Doing more than the maximum sockets the process is allows |
| 66 | causes strangeness to occur in libevent.. somehow |
| 67 | it is getting around to epoll_add which is causing valgrind |
| 68 | to barf. |
| 69 | * Added cheap protection code for failures in callback handlers |
| 70 | ====== |
| 71 | 0.0.0 - 2007-06-10 12:00 EST |
| 72 | Initial public version, was broken due to self-resume coroutines |