On Monday, 9 May 2016 at 09:35:18 UTC, sigod wrote:
On Monday, 9 May 2016 at 08:55:36 UTC, Jonathan M Davis wrote:
But given that std.net.curl handles stuff like SSL/TLS, we
_can't_ actually replace all of its functionality - at least
not without adding a dependency on a different C library,
since there's no way that it's sane to do the crypto stuff
ourselves without a crypto expert, and even then, we should
think twice about it. I could see implementing the SSL/TLS
protocols themselves but not the crypto they use. If we
replace std.net.curl, we likely should just provide the basic
HTTP functionality, and leave the rest to a dub package that
we move std.net.curl to.
Any chances that we can produce good crypto code over time? And
verify it with experts, of course.
https://github.com/etcimon/botan AFAIK, it is already used in
production by its author, in combination with libasync + vibe.d +
http2 for a full stack D solution.
...
