Re: [Libevent-users] Opaque data on callback?

2010-12-30 Thread Harlan Stenn
Thanks for the response, Kelly. Kelly wrote: > Perhaps I'm missing something but the callback for async dns is: > > _lookup_response( int errCode, struct evutil_addrinfo* info, void* data ) > > Where the "data" member is what you pass into evdns_getaddrinfo and can be > anything you want.

[Libevent-users] bug + question

2010-12-30 Thread Mihai Draghicioiu
Hi all. I've found that evhttp_parse_query_str only works if the query string is of the form foo=bar&baz=quux. If we have a query string of the form foo=bar&baz (no value for the last key), it fails. I consider this a bug, because you have all the other valid parameters in there, and it can just se

RE: [Libevent-users] Opaque data on callback?

2010-12-30 Thread Kelly Brock
Hi Harlan, Perhaps I'm missing something but the callback for async dns is: _lookup_response( int errCode, struct evutil_addrinfo* info, void* data ) Where the "data" member is what you pass into evdns_getaddrinfo and can be anything you want. So, you already have a place to put your co

[Libevent-users] Opaque data on callback?

2010-12-30 Thread Harlan Stenn
I'm new to libevent... I'm writing an app that needs async DNS. While I have the core of this working, I have some "private data" that I want to associate with each name that is being looked up, so it would be Swell if the evutil_addrinfo was actually a structure that contained: - a void pointer