Hi. I'm trying to figure out how to set myself up to have
bufferevents do "most of my work" for me, trying to read
messages over non-blocking network sockets.
I am figuring out how to get them set up, and I just need
to call bufferevent_new to make one, and pass it the
various callbacks. Do I need the struct bufferevent* that
is returned for anything other than free'ing it when I'm
done? Can I, when I've finished the work I need to do
(reading a single message in its entirety) just delete
it from within the callback? I would assume...
I'm looking at the high and low watermarks. I can
tell from the code that setting the low watermark will
prevent the callback from being called before that
many bytes are available (for read, in my case).
I can't quite tell from the code, tho, what effect setting
the high water [read] mark has. It seems to have a
slightly different callback set up in that case, but
since I'm new to this, I can't tell excatly what the difference
in effect is. Could anyone describe that quickly?
Thanks...
- Chris
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkey.org/mailman/listinfo/libevent-users
