Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
We need to upgrade and secure the HTTP servers backing the JSON-RPC and Prometheus end-points #358
Currently, out JSON-RPC server is based on Chronos, but offers only HTTP 1.0 compatibility.
The Prometheus server runs in a separate thread and uses
For more in-depth discussion, please see this thread:
We need to develop a production-ready server that we'll be able to use for both end-points (potentially from a single thread).
That wouldn't have been a problem. It only supports the "application/json" content type: https://github.com/status-im/nim-json-rpc/blob/de05184c740095a2f3f6f61ff90e5aed0e83d5d8/json_rpc/servers/httpserver.nim#L76
we welcome the community to port the changes and improvements we develop, or alternatively remove asynchttp from std lib into a separate library and take it from there.
as discussed at length and many times, our goals for chronos differ from those of the std lib significantly, as does the development model.