Hey, With the initial Nimbus release out, we're back to working on features - this is good news for chronos, because we've finally been able to put in place some more nice pieces of the puzzle: we now have both a minimal HTTP(S) client and server in beta :)
Some features: * Security first - we will be using the server in Nimbus which along with the rest of the code (eventually) goes through review, audit and scrutiny, being covered by security bounties * SSL out of the box, no separate openssl library needed on any platform * Cancellation support * Initial support for exception effect tracking (more to come) * Low memory footprint In Nimbus, chronos above all drives the peer-to-peer networking through [nim-libp2p](https://github.com/status-im/nim-libp2p) \- our first uses of the web server is to expose [metrics](https://github.com/status-im/nim-metrics) and a [REST API](https://github.com/status-im/nim-presto/) in addition to the existing [JSON-RPC](https://github.com/status-im/nim-json-rpc/) server. Next up is likely WebSockets support, such that libp2p can learn to interop with browsers more smoothly :) If you're looking for something more of a web framework, bung87's been at it with a chronos-based one - [scorper](https://github.com/bung87/scorper/) \- make sure to check that out as well!
