Searched hist:2014 (Results 1 – 8 of 8) sorted by relevance
/unit/src/ |
H A D | nxt_external.c | diff 2014:f8a0992944df Wed Nov 24 10:11:00 UTC 2021 Max Romanov <max.romanov@nginx.com> Sending shared port to application prototype.
Application process started with shared port (and queue) already configured. But still waits for PORT_ACK message from router to start request processing (so-called "ready state").
Waiting for router confirmation is necessary. Otherwise, the application may produce response and send it to router before the router have the information about the application process. This is a subject of further optimizations.
|
H A D | nxt_unit.h | diff 2014:f8a0992944df Wed Nov 24 10:11:00 UTC 2021 Max Romanov <max.romanov@nginx.com> Sending shared port to application prototype.
Application process started with shared port (and queue) already configured. But still waits for PORT_ACK message from router to start request processing (so-called "ready state").
Waiting for router confirmation is necessary. Otherwise, the application may produce response and send it to router before the router have the information about the application process. This is a subject of further optimizations.
|
H A D | nxt_application.h | diff 2014:f8a0992944df Wed Nov 24 10:11:00 UTC 2021 Max Romanov <max.romanov@nginx.com> Sending shared port to application prototype.
Application process started with shared port (and queue) already configured. But still waits for PORT_ACK message from router to start request processing (so-called "ready state").
Waiting for router confirmation is necessary. Otherwise, the application may produce response and send it to router before the router have the information about the application process. This is a subject of further optimizations.
|
H A D | nxt_port.c | diff 2014:f8a0992944df Wed Nov 24 10:11:00 UTC 2021 Max Romanov <max.romanov@nginx.com> Sending shared port to application prototype.
Application process started with shared port (and queue) already configured. But still waits for PORT_ACK message from router to start request processing (so-called "ready state").
Waiting for router confirmation is necessary. Otherwise, the application may produce response and send it to router before the router have the information about the application process. This is a subject of further optimizations.
|
H A D | nxt_application.c | diff 2014:f8a0992944df Wed Nov 24 10:11:00 UTC 2021 Max Romanov <max.romanov@nginx.com> Sending shared port to application prototype.
Application process started with shared port (and queue) already configured. But still waits for PORT_ACK message from router to start request processing (so-called "ready state").
Waiting for router confirmation is necessary. Otherwise, the application may produce response and send it to router before the router have the information about the application process. This is a subject of further optimizations.
|
H A D | nxt_main_process.c | diff 2014:f8a0992944df Wed Nov 24 10:11:00 UTC 2021 Max Romanov <max.romanov@nginx.com> Sending shared port to application prototype.
Application process started with shared port (and queue) already configured. But still waits for PORT_ACK message from router to start request processing (so-called "ready state").
Waiting for router confirmation is necessary. Otherwise, the application may produce response and send it to router before the router have the information about the application process. This is a subject of further optimizations.
|
H A D | nxt_unit.c | diff 2014:f8a0992944df Wed Nov 24 10:11:00 UTC 2021 Max Romanov <max.romanov@nginx.com> Sending shared port to application prototype.
Application process started with shared port (and queue) already configured. But still waits for PORT_ACK message from router to start request processing (so-called "ready state").
Waiting for router confirmation is necessary. Otherwise, the application may produce response and send it to router before the router have the information about the application process. This is a subject of further optimizations.
|
H A D | nxt_router.c | diff 2014:f8a0992944df Wed Nov 24 10:11:00 UTC 2021 Max Romanov <max.romanov@nginx.com> Sending shared port to application prototype.
Application process started with shared port (and queue) already configured. But still waits for PORT_ACK message from router to start request processing (so-called "ready state").
Waiting for router confirmation is necessary. Otherwise, the application may produce response and send it to router before the router have the information about the application process. This is a subject of further optimizations.
|