On 1 feb 2012, at 23:31, Nick Mathewson wrote:
> … [ questions about POSIX signals and pthreads ] …
> …
> Sadly, this whole business is a huge pile of gunk.
Thanks for the epic reply, Nick.
I did some additional research before diving into my POSIX signal plan and it
indeed looks like a huge mes
On 19 jan 2012, at 21:53, Nick Mathewson wrote:
> …
> The usual way is with events that you manually activate. You'll need
> to use libevent 2 for threading support, and call one of the
> appropriate functions at startup time to turn on threading support.
I've been thinking about this over the pa
On 20 jan 2012, at 17:17, Nick Mathewson wrote:
> …
> As a defense-in-depth mechanism, I'd say "sure, go ahead", but IMO
> you'd get more benefit against as-yet-unknown vulnerabilities with the
> usual techniques, like non-executable heap/stack, randomized address
> spaces, etc.
Thanks again for t
On 19 jan 2012, at 22:00, MigueL DíaZ wrote:
> …
> I'd second that idea. Unless you intend to use the same code/protocol you use
> for you inter-thread communication in a network environment, using evbuffer
> might be just an overkill.
Thanks for the tips, Nick and Miguel – they made me rethink
main problem I have is conceptual: how can I create
an application where clients are notified of 'events' that happen outside of a
libevent event loop. I would like to (re)use as much of libevent as possible.
Thanks in advance for your time everyone, I'll gladly elaborate if so d
