Okay. Then I'm beginning to develop(slowly) new version of "event" extension.

Wez,

I'll drop a post to the mailing list(and you) when it's done.

On 01/02/2013 11:16 PM, Wez Furlong wrote:
I don't believe anyone is actively working on these any more, it would make
sense for someone to take ownership.


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)



--
Regards,

Ruslan Osmanov

http://osmanov-dev-notes.blogspot.com | @ruslan_osmanov | +998916818499

--
PECL development discussion Mailing List (http://pecl.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to