[Libevent-users] libevent 1.2 varargs bug

Hello. i've been trying to 'make verify' libevent-1.2 on x86-64 SLES9 (gcc 3.3.3, glibc 2.3.5 (20050720) ) system. it just segfaults on regress evbuffer test, i've tracked the issue down to the loop calling vsnprintf() inside evbuffer_add_vprintf() the problem is that you can't call vsnprintf()

Re: [Libevent-users] libevent 1.2

On Wed, Oct 18, 2006 at 09:39:14PM +0200, Rhythmic Fistman wrote: > >From: William Ahern <[EMAIL PROTECTED]> > > >On Wed, Oct 18, 2006 at 12:21:17AM -, Christopher Baus wrote: > >> I'm not recommending that this should be in libevent, but if you are > >> looking for something that abstracts ou

Re: [Libevent-users] libevent 1.2

From: William Ahern <[EMAIL PROTECTED]> On Wed, Oct 18, 2006 at 12:21:17AM -, Christopher Baus wrote: > I'm not recommending that this should be in libevent, but if you are > looking for something that abstracts out both IOCP and non-blocking > sockets, ASIO is a good place to start. > I wo

Re: [Libevent-users] libevent 1.2

On Wed, Oct 18, 2006 at 12:11:20PM -0700, Scott Lamb wrote: > On Oct 18, 2006, at 11:49 AM, William Ahern wrote: > >On Wed, Oct 18, 2006 at 12:04:11AM -0600, Jason Ish wrote: > >>I ran across at least one criticism of libevent gaining too much > >>other > >>than pure event library: > >>http://var

Re: [Libevent-users] libevent 1.2

Hi There! Completely  agree with you, William. If you need a feature, spend time to add it. cheers Younès William Ahern a écrit : On Wed, Oct 18, 2006 at 12:04:11AM -0600, Jason Ish wrote: I ran across at least one criticism of libevent gaining too much other than pure event libra

Re: [Libevent-users] libevent 1.2

On Oct 18, 2006, at 11:49 AM, William Ahern wrote: On Wed, Oct 18, 2006 at 12:04:11AM -0600, Jason Ish wrote: I ran across at least one criticism of libevent gaining too much other than pure event library: http://varnish.projects.linpro.no/wiki/EventLibrary All of these criticisms are parti

Re: [Libevent-users] libevent 1.2

On Wed, Oct 18, 2006 at 12:04:11AM -0600, Jason Ish wrote: > I ran across at least one criticism of libevent gaining too much other > than pure event library: > http://varnish.projects.linpro.no/wiki/EventLibrary > All of these criticisms are partially or wholly invalid. The DNS and HTTP code is

Re: [Libevent-users] libevent 1.2

Thanks, I'll check it out.I don't really have any urgent need.  I had done a project a while ago that used asynchronous networking tied to an event loop.  I origninally wanted to use python for it so I mocked it up using python and its asnycore module.  Worked fairly well except for the traditional

Re: [Libevent-users] libevent 1.2

From: "Christopher Baus" <[EMAIL PROTECTED]> > Has there been much interest in an IOCP port for libevent? I would > certainly be interested. > I even started working on a rough port, but as mentioned IOCP is proactive > rather than reactive, > (ie you tell it how much to read/send and the eve

Re: [Libevent-users] libevent 1.2

On Mon, Oct 16, 2006 at 10:18:28PM -0700, Niels Provos wrote: > Hi everyone, > > libevent 1.2 was released yesterday. There are some major feature > improvements: > > - Support for non-blocking DNS resolution > - Support for lightweight HTTP clients and servers > - Support for Sun's Event Port

Re: [Libevent-users] libevent 1.2

Hi Gordon, On 10/18/06, Gordon Scott <[EMAIL PROTECTED]> wrote: Has there been much interest in an IOCP port for libevent? I would certainly be interested. I even started working on a rough port, but as mentioned IOCP is proactive rather than reactive, (ie you tell it how much to read/send an

Re: [Libevent-users] libevent 1.2

On Wed, Oct 18, 2006 at 12:21:17AM -, Christopher Baus wrote: > > >> The slickest implementation I've seen that works with *nix non-blocking > >> I/O and Windows IOCP is boost ASIO http://asio.sourceforge.net/. > >> Instead > >> of modeling reactive behavior with IOCP, it mimics proactive beha

Re: [Libevent-users] libevent 1.2

>> The slickest implementation I've seen that works with *nix non-blocking >> I/O and Windows IOCP is boost ASIO http://asio.sourceforge.net/. >> Instead >> of modeling reactive behavior with IOCP, it mimics proactive behavior on >> *nix. It works out surprisingly well. > > I'm privy to my own [C

Re: [Libevent-users] libevent 1.2

On Tue, Oct 17, 2006 at 11:33:30PM -, Christopher Baus wrote: > > Has there been much interest in an IOCP port for libevent? I would > > certainly be interested. > > I even started working on a rough port, but as mentioned IOCP is proactive > > rather than reactive, > > (ie you tell it how mu

Re: [Libevent-users] libevent 1.2

> Has there been much interest in an IOCP port for libevent? I would > certainly be interested. > I even started working on a rough port, but as mentioned IOCP is proactive > rather than reactive, > (ie you tell it how much to read/send and the event tells you that) and it > got rather awkward pr

Re: [Libevent-users] libevent 1.2

>>Neato! Seems you've subsumed most OS event waiting interfaces.>>Does that include win32 IOCPs (io completion ports) yet?>>If not, they're definitely worth a look. However, they're not very >>"selecty", in that they scale well and they tell you when something>>has actually happened instead of when

Re: [Libevent-users] libevent 1.2

On Oct 17, 2006, at 11:08 AM, Rhythmic Fistman wrote: That's funny, there doesn't seem to be a self-pipe-trick implementation in lib-evt... how do you get by without it? There is, although it uses a socketpair() instead of a pipe(). -- Scott Lamb _

Re: [Libevent-users] libevent 1.2

On 10/17/06, Scott Lamb <[EMAIL PROTECTED]> wrote: On Oct 17, 2006, at 12:19 PM, Rhythmic Fistman wrote:> On 10/17/06, Scott Lamb <[EMAIL PROTECTED]> wrote:>> On Oct 17, 2006, at 11:08 AM, Rhythmic Fistman wrote: >> > That's funny, there doesn't seem to be a self-pipe-trick>> > implementation in li

Re: [Libevent-users] libevent 1.2

On Oct 17, 2006, at 12:19 PM, Rhythmic Fistman wrote: On 10/17/06, Scott Lamb <[EMAIL PROTECTED]> wrote: On Oct 17, 2006, at 11:08 AM, Rhythmic Fistman wrote: > That's funny, there doesn't seem to be a self-pipe-trick > implementation in lib-evt... how do you get by without it? There is, althou

Re: [Libevent-users] libevent 1.2

On 10/17/06, Scott Lamb <[EMAIL PROTECTED]> wrote: On Oct 17, 2006, at 11:08 AM, Rhythmic Fistman wrote: > That's funny, there doesn't seem to be a self-pipe-trick > implementation in lib-evt... how do you get by without it? There is, although it uses a socketpair() instead of a pipe(). Ah, I

Re: [Libevent-users] libevent 1.2

From: "Niels Provos" <[EMAIL PROTECTED]> libevent 1.2 was released yesterday. There are some major feature improvements: - Support for non-blocking DNS resolution - Support for lightweight HTTP clients and servers - Support for Sun's Event Ports Neato! Seems you've subsumed most OS event w

Re: [Libevent-users] libevent 1.2

At Mon, 16 Oct 2006 22:18:28 -0700, Niels Provos wrote: > > Hi everyone, > > libevent 1.2 was released yesterday. There are some major feature > improvements: > > - Support for non-blocking DNS resolution > - Support for lightweight HTTP clients and servers Support for > - Sun's Event Ports

[Libevent-users] libevent 1.2

Hi everyone, libevent 1.2 was released yesterday. There are some major feature improvements: - Support for non-blocking DNS resolution - Support for lightweight HTTP clients and servers - Support for Sun's Event Ports There have also been several bugfixes. I hope this works on your system.