tcp

Is your feature request related to a problem? Please describe.
SIEC is currently the default curve, despite it being unknown and receiving insufficient cryptanalysis. It looks as if it was chosen because you're related to the designer. Then the NIST curves have seeds that haven't been explained, lea

这里的路由和server通信是否可以用一个长连接来维护更好

This was uncovered in the process of reviewing #608. See my comments there for more.

In short, wrap-future checks .isSuccess on a future, when it really means to check .isDone. If it succeeded, it creates an immediate success-deferred. If not, it attaches handlers. In the case of a failed/canceled future, it does a lot of unnecessary work before immediately invoking the handler: fn thread

We had an issue where an api user was using the incorrect parameters on an API call. Having this feature would have made the API fail instead of proceeding. The bug would been found earlier.

I can see where this would be a hassle on many cases, But it would be nice for new projects.

I suppose it could be a global config item that could be overridden at the individual action level:

For