Kip

I think this is a good idea, but probably fairly complicated to implement. PRs welcome.

I should add that versioning as it actually is in the source is a 3-tuple. e.g. I think what we're talking about is releasing version 0.1.0. To bump the version...

Hey @mohsenomidi. Sorry, but I'm sadly not the right guy for this. I could probably help if I had time, but right now it's very limited.

Happy to learn you've gotten further in your discovery. When you're ready for a PR, feel free to submit it.

> @kiplingw, @dennisjenkins75, I was thinking about tagging the current master branch as Pistache 0.0.5, so that I can finally start on packaging it for Debian. It this fine for...

Thanks @Tachi107. I've let @pabs3 know. I think we're still [awaiting](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929593) a Debian maintainer.

> @pabs3 thanks for reminding me of the RFS. By the way, I've been uploading packages for a while now, I'm a DM :D YES!!!

I was wondering the same. The Request class has a method peer(), but it appears to be ommitted at compile time in http.h: ` #ifdef LIBSTDCPP_SMARTPTR_LOCK_FIXME std::shared_ptr peer() const; #endif

Thanks @btwear. Other than when the endpoint handler is invoked, where else would the user be expected to handle the same request? For passing custom data around, assuming there was...

In short they're queued. Pistache requires 6N + 5 file descriptors for each service thread it spawns. The 5 is the number it starts with before any threads. On the...