> multithreading the focus of this release has been on security, stability and feature completeness, mainly because we haven't yet reached the point where http performance is an actual bottleneck anywhere (ie when we benchmark whole-application performance, it's not the http part that stands out, but that's tightly related to the kind of processing out applications do) - ie it's by no means slow, but I have no doubt there are faster alternatives out there that target specific benchmarks. ymmv with the kind of workload you put on it - happy to hear back on this front if you find some particular weaknesses.
There are some loose plans to look more into multithreading for 5.0, ie a multithreaded connection delegator, that kind of stuff but .. > Is this designed to work well with ARC/ORC? ORC has not yet been released at a quality level that is compatible with our needs - we keep an eye on it and as mentioned elsewhere, the chronos core is cycle-free meaning it's at least theoretically can work with ARC, so when ORC reaches the point of usability, we'll be in a good spot. That said, I suspect proper support is a chronos 5.0 concern when a newer Nim is out and to fully take advantage of ORC most nim code "out there" will need a thorough review (much like when r-value references hit C++11) even if it seems to work passably today.
