mirror of
https://github.com/nginx/nginx.git
synced 2026-10-22 20:11:17 +00:00
Resolver: added the "async" flag to resolver context.
The flag indicates that the resolve handler is called asynchronously after the resolve function ngx_resolve_name()/ngx_resolve_addr() exited.
This commit is contained in:
parent
b0b24e8a30
commit
439e205255
2 changed files with 7 additions and 1 deletions
|
|
@ -746,6 +746,7 @@ ngx_resolve_name_locked(ngx_resolver_t *r, ngx_resolver_ctx_t *ctx,
|
|||
last->next = rn->waiting;
|
||||
rn->waiting = ctx;
|
||||
ctx->state = NGX_AGAIN;
|
||||
ctx->async = 1;
|
||||
|
||||
do {
|
||||
ctx->node = rn;
|
||||
|
|
@ -892,6 +893,7 @@ ngx_resolve_name_locked(ngx_resolver_t *r, ngx_resolver_ctx_t *ctx,
|
|||
rn->waiting = ctx;
|
||||
|
||||
ctx->state = NGX_AGAIN;
|
||||
ctx->async = 1;
|
||||
|
||||
do {
|
||||
ctx->node = rn;
|
||||
|
|
@ -1023,6 +1025,7 @@ ngx_resolve_addr(ngx_resolver_ctx_t *ctx)
|
|||
ctx->next = rn->waiting;
|
||||
rn->waiting = ctx;
|
||||
ctx->state = NGX_AGAIN;
|
||||
ctx->async = 1;
|
||||
ctx->node = rn;
|
||||
|
||||
/* unlock addr mutex */
|
||||
|
|
@ -1119,6 +1122,7 @@ ngx_resolve_addr(ngx_resolver_ctx_t *ctx)
|
|||
/* unlock addr mutex */
|
||||
|
||||
ctx->state = NGX_AGAIN;
|
||||
ctx->async = 1;
|
||||
ctx->node = rn;
|
||||
|
||||
return NGX_OK;
|
||||
|
|
@ -3019,6 +3023,7 @@ ngx_resolver_srv_names_handler(ngx_resolver_ctx_t *cctx)
|
|||
srv = cctx->srvs;
|
||||
|
||||
ctx->count--;
|
||||
ctx->async |= cctx->async;
|
||||
|
||||
srv->ctx = NULL;
|
||||
srv->state = cctx->state;
|
||||
|
|
|
|||
|
|
@ -218,7 +218,8 @@ struct ngx_resolver_ctx_s {
|
|||
void *data;
|
||||
ngx_msec_t timeout;
|
||||
|
||||
ngx_uint_t quick; /* unsigned quick:1; */
|
||||
unsigned quick:1;
|
||||
unsigned async:1;
|
||||
ngx_uint_t recursion;
|
||||
ngx_event_t *event;
|
||||
};
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue