mark

An interesting feature would be to monitor average RTT between the client and server; create a lower resolution version of any new requests, and cache them for later!

@buaazp interestingly enough; I'm refactoring a bit on zimg right now. It's something to do, and hopefully be a good sport about testing new libevent & evhtp features.

Not quite sure this is the right place for these things to go. But that can be figured out. I would check out the current develop branch here: https://github.com/ellzey/libevhtp/tree/develop the...

I heard a rumor evhtp is going away! What can I do to make that not happen?

nothing, I just saw a paper saying that On Mon, Oct 19, 2015 at 8:52 PM 招牌疯子 [email protected] wrote: > @ellzey https://github.com/ellzey > Bad news! 😱what's happening? > > —...

On 10/19, deleisha wrote: > Will be libevent be interested in another TLS implementation, Yes, as long as the license of the implementation does not conflict with the BSD license...

At a second glance we do use bio's for the betas _shudder_. I would like to get a list of what functionality users need to properly abstract to the point...

I did a bit of researching (googling), and I found that libcurl has a decent enough hooking api for ssl. Though it's not table based, it has to be done...

Note: each entry in `./src/event2/` will have it's corresponding include file, which will include the files found within the directory. i.e., `./src/event2/http.h` will be ``` C #ifndef __EVENT_HTTP_H__ #define __EVENT_HTTP_H__...

With the current cmake configuration, it literally makes a fake layout to do exactly this. But in this case, nothing needs to be changed. Not even from the user's perspective.