I don't believe anyone is actively working on these any more, it would make sense for someone to take ownership.
--Wez. On Wed, Jan 2, 2013 at 4:59 AM, Julien Pauli <[email protected]> wrote: > On Wed, Jan 2, 2013 at 1:24 PM, Ruslan Osmanov <[email protected]>wrote: > >> Hi, >> >> Is `event' PECL extension still maintained? I'm thinking of writing new >> one, since both `event' and `libevent' don't support libevent 2. >> >> I could contribute to libevent's code. But there is deprecated/changed >> API in libevent 2. Also, "libevent" isn't good name for extension(I know, >> "event" extension was already there...). >> >> Thus, if `event' extension is no longer maintained, I'd like to use this >> name for a new extension. Or, maybe you would suggest another name. Ehm, >> "AnyEvent", "YAEvent"("yet another event" :), "events", >> "ooevent"("object-oriented event" [I'd like to make OO API])... :-/ >> >> So what's better: >> >> - a new extension with different name(e.g. "OOEvent") >> >> - fork libevent, make it compatible with libevent 2, add new functions, >> request merge; >> >> - fork libevent, make it compatible with libevent 2, add new functions, >> request merge? >> >> The main purpose is to add libevent 2 API support and some missing >> functions(e.g. ssl and http stuff) >> > > Hello, > > I don't think ext/event is maintained anymore, as the last release is back > from 2004. > ext/libevent should be maintained thought not very active. > > Wait for their main authors to reply this mail, perhaps you could merge > your work with theirs ;-) > > Julien.Pauli >
