|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
|
Translation changed |
|
Traditionally, programs use a传统做法是,程序使用 [@boost:/doc/html/boost_asio/reference/steady_timer.html `net::steady_timer`]to determine when a timeout occurs, and then call来检测超时,然后调用套接字的 [@boost:/doc/html/boost_asio/reference/basic_socket/close/overload2.html `close`]on the socket to release the resources. The complexity of managing a separate timer is often a source of方法释放资源。对于非专业人士,单独管理一个计时器所带来的复杂性,常常让人感到 [@http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1269r0.html#timersfrustration] for non-experts.困扰]。