keep a reference of ngx_conneciton_t to the ngx_quic_path_t?

[Sergey Kandaurov]

> On 7 Sep 2023, at 12:49, Yu Zhu <pl080516 at gmail.com> wrote:
> 
> Hi
> 
> Some function declarations contain ngx_connection_t and quic_quic_path_t:
> 	• ngx_int_t ngx_quic_send_new_token(ngx_connection_t *c, ngx_quic_path_t *path);
> 	• ngx_quic_path_limit(ngx_connection_t *c, ngx_quic_path_t *path, size_t size)
> 	• void ngx_quic_discover_path_mtu(ngx_connection_t *c, ngx_quic_path_t *path)
> 	• static ngx_int_t ngx_quic_expire_path_mtu_discovery(ngx_connection_t *c, ngx_quic_path_t *path);
> 	• static ngx_int_t ngx_quic_expire_path_validation(ngx_connection_t *c, ngx_quic_path_t *path)
> 	• static ngx_int_t ngx_quic_expire_path_mtu_delay(ngx_connection_t *c, ngx_quic_path_t *path)
> 	• static ngx_int_t ngx_quic_send_path_challenge(ngx_connection_t *c, ngx_quic_path_t *path);
> 	• ... and others...
>  Is it possible to keep a reference of ngx_connection_t to the ngx_quic_path_t?
> 

An active path is kept in qc->path.
There may be other paths accessible through the qc->paths queue.
That's why such functions have a distinct path argument.

-- 
Sergey Kandaurov