... why would you want to use bufferevent for this?
You really want something like bufferevent, except:
* You want to attach source/destination IP:port info, as an option;
* You want to support scatter/gather IO as an option;
* You want to be able to have well defined boundaries - ie, "This is a
On Wednesday, December 12, 2012 12:12 PM Nick Mathewson wrote
> I'm pretty sure John is asking about UDP support under bufferevents.
Actually I was looking for any UDP support - it doesn't have to necessarily use
bufferevents. I've figured out how to get UDP working with writing my own
socket in
Nick Mathewson wrote:
I'm pretty sure John is asking about UDP support under bufferevents.
That's nontrivial.
The last time I looked, it appeared that the socket-backed
bufferevent code was almost exactly right for a UDP transition, but
that the underlying evbuffer objects didn't have a lot of
On Wed, Dec 12, 2012 at 1:56 PM, Scott Dorr wrote:
> UDP works fine in libevent. I have several UDP based applications that run
> solely over UDP.
>
> You might have to run edge triggered to support UDP. I know I had to move to
> edge triggered, though I can't recall if that was for UDP, or for
UDP works fine in libevent. I have several UDP based applications that run
solely over UDP.
You might have to run edge triggered to support UDP. I know I had to move to
edge triggered, though I can't recall if that was for UDP, or for the OS I was
using, or a combination.
- scott
Sent from
Has there been any progress on UDP support in libevent? The last mention I can
find in the email list is from Dec 2010. It sounded like supporting unconnected
sockets was going to be difficult in 2.0.x - will any of the changes in 2.1.x
make this easier?
I'm not familiar enough with libevent t
