Problem: zap_msg_available duplicated between curve_server_t and plain_server_t…
Problem: zap_msg_available duplicated between curve_server_t and plain_server_t (with deviating behaviour) Solution: pull up into zap_client_common_handshake_t, along with handle_zap_status_code and error_detail/current_error_detail
Showing
Please
register
or
sign in
to comment