Re: [Libevent-users] Re: [Levent-commits] [Libevent/master 3/4] Add doxygen for event_base_dump_events

2012-09-06 Thread Roman Puls
Am 06.09.2012 17:44, schrieb Nick Mathewson: On Thu, Sep 6, 2012 at 8:40 AM, Roman Puls wrote: Hi Nick, excellent - it would be even greater to specify a callback procedure receiving the struct event tokens (I currently write language bindings for tcl, and it would be great to generate the

[Libevent-users] Re: [Levent-commits] [Libevent/master 3/4] Add doxygen for event_base_dump_events

2012-09-06 Thread Roman Puls
Hi Nick, excellent - it would be even greater to specify a callback procedure receiving the struct event tokens (I currently write language bindings for tcl, and it would be great to generate the textual representation myself) But why I write: shouldn't that stuff (event_base_dump_events) b

[Libevent-users] locking / termination callback

2011-10-21 Thread Roman Puls
Hi Nick and friends, just a question and an idea: 1. locking assuming event_base supports and has a lock, is there an API to expose that particular lock towards the application? In some situations, it would help to avoid complex designs by sharing the lock. API could be like "int event_base_l

Re: [Libevent-users] http server and infinite streams

2011-05-10 Thread Roman Puls
On May 07.05.2011 20:26, Mark Ellzey wrote: On Sat, May 07, 2011 at 01:07:40AM -0400, Nick Mathewson wrote: *lots of text here* One of the ways nginx deals with very large streams of data is to actually spool the data to file. By default this is turned off. But this may be a simple solution to

[Libevent-users] levent 2.x multithreaded?

2010-03-18 Thread Roman Puls
Hi Folks, I thought libevent would work multithreaded in the sense we can create (let's say) 4 worker threads that poll the same event_base. Is that assumption wrong? In my test code, I see deadlocks between the worker-threads inside libevent after the first event getting dispatched via sock