On Sun, Feb 12, 2006 at 05:50:11PM -0800, Niels Provos wrote: > I think I found a workable solution that leaves the user with total > control if desired but otherwise achieves a reasonable behavior, too.
The growth limitation works great for what most applications will ever expect to see, and is certainly better than getting the whole chunk at once. Normal behavior without the watermark set is less painful than before, though apps may start to feel the pain once the buffer grows to 16MB and beyond. At least now there are opportunities for the app to set the watermark to curb the growth at a sensible level. Using the high watermark does the right thing. The buffer grows up to the watermark and stays fixed, giving the lowest latency on the first block read and then growing to the watermark. I like this behavior even better than the first patch. cheers --chris _______________________________________________ Libevent-users mailing list [email protected] http://monkey.org/mailman/listinfo/libevent-users
