mirror of
https://github.com/vercel-labs/scriptc.git
synced 2026-10-26 06:34:20 +08:00
Chris Tate
91e15f3426
child_process and http2 events ran with no store, or with the context of whichever socket dispatch delivered them. Node runs them in the context of the handle or request that produces them. child_process: a child, its piped stdout, stderr and stdin, and its IPC channel keep the context of the spawn() or fork() call. 'spawn', 'error', 'exit', 'close', stdout's and stderr's 'data' and 'end', and the channel's 'message' and 'disconnect' run in it, in the POSIX and the Windows implementations. stdin's 'drain' and 'error' run in the context of the latest write() call, its 'finish' in the context of its end() call, and a send() callback in the context of its send() call. http2: a session keeps the context it was created in, the http2.connect() call for a client and the server's listen() context for a server session, and the session's socket callbacks and deferred emits run in it. A client stream keeps the context of its request() call, and the frames that drive a stream's events (DATA, WINDOW_UPDATE, RST_STREAM, and a client's HEADERS) and its deferred emits run in the stream's context. A session remembers the stream its last lookup by id found, so the context lookup and the frame's own handling share one search. A server stream and its compatibility request and response run with no store, as Node's do. An accepted h2c socket's own events run with no store, as an accepted net socket's do, so a server.close() that waits for its sessions calls back with no store; a TLS server's sockets keep the listen() context, as before. Corpus 7385 to 7389.