/libuv/docs/code/multi-echo-server/ |
H A D | hammer.js | 4 var write = function(socket) { function 5 socket.write(PHRASE, 'utf8'); 15 write(socket); 17 write(socket);
|
/libuv/docs/src/ |
H A D | stream.rst | 30 this type. When a stream is in non-blocking mode, write requests sent 95 Pointer to the stream where this write request is running. 99 Pointer to the stream being sent using this write request. 109 Shutdown the outgoing (write) side of a duplex stream. It waits for pending 110 write requests to complete. The `handle` should refer to a initialized stream. 166 /* Logic which handles the write result */ 192 Extended write function for sending handles over a pipe. The pipe must be 202 Same as :c:func:`uv_write`, but won't queue a write request if it can't be 213 Same as :c:func:`uv_try_write` and extended write function for sending 246 is changed after write requests have already been submitted. Therefore it is
|
H A D | poll.rst | 20 write to the fd. 98 shutdown path because an extra read or write call might be avoided. 123 readable/writable and the callback did not conduct a read/write on 127 * The callback committed a write on the socket, but it remained
|
H A D | design.rst | 36 handle: write requests are used to write data on a handle; or standalone: getaddrinfo requests 53 (readable, writable hangup) so handles can read, write or perform the desired I/O operation. 95 for a read or write operation get their callbacks called at this point.
|
H A D | fs.rst | 262 crash if the memory mapped write operation fails. 390 create a copy-on-write reflink. If the underlying platform does not 391 support copy-on-write, or an error occurs while attempting to use 392 copy-on-write, a fallback copy mechanism based on 395 attempt to create a copy-on-write reflink. If the underlying platform does 396 not support copy-on-write, or an error occurs while attempting to use 397 copy-on-write, then an error is returned. 567 The file is opened in append mode. Before each write, the file offset is 674 Open the file for read-write access. 717 successfully for write access, its length shall be truncated to zero. [all …]
|
H A D | version.rst | 10 will allow you to write or compile code conditionally, in order to work with
|
H A D | threading.rst | 37 Read-write lock data type. 184 Read-write locks
|
/libuv/test/ |
H A D | run-tests.c | 172 r = write(3, out, sizeof(out) - 1); in maybe_run_test() 235 ASSERT_EQ(1, write(closed_fd, "x", 1)); in maybe_run_test() 237 ASSERT_EQ(-1, write(closed_fd, "x", 1)); in maybe_run_test()
|
H A D | test-fork.c | 209 ASSERT_EQ(1, write(sync_pipe[1], "1", 1)); /* alert child */ in TEST_IMPL() 287 ASSERT_EQ(1, write(sync_pipe[1], "1", 1)); /* alert parent */ in TEST_IMPL() 346 ASSERT_EQ(1, write(sync_pipe2[1], "1", 1)); /* alert child */ in TEST_IMPL() 355 ASSERT_EQ(1, write(sync_pipe[1], "1", 1)); /* alert parent */ in TEST_IMPL()
|
H A D | test-eintr-handling.c | 54 nwritten = write(pipe_fds[1], test_buf, sizeof(test_buf)); in thread_main()
|
H A D | runner-unix.c | 225 r = write(args->pipe[1], "", 1); in dowait()
|
H A D | test-spawn.c | 858 uv_write_t write; in TEST_IMPL() local 888 r = uv_write(&write, (uv_stream_t*) &in, &buf, 1, write_cb); in TEST_IMPL() 2047 w = write(1, pbuf, (size_t)c); in spawn_stdin_stdout()
|
/libuv/ |
H A D | Makefile.am | 272 test/test-tcp-connect-error-after-write.c \ 282 test/test-tcp-shutdown-after-write.c \ 285 test/test-tcp-write-to-half-open-connection.c \ 286 test/test-tcp-write-after-connect.c \ 288 test/test-tcp-write-fail.c \ 289 test/test-tcp-try-write.c \ 290 test/test-tcp-write-in-a-row.c \ 291 test/test-tcp-try-write-error.c \ 292 test/test-tcp-write-queue-order.c \
|
H A D | CMakeLists.txt | 516 test/benchmark-tcp-write-batch.c 644 test/test-tcp-connect-error-after-write.c 656 test/test-tcp-shutdown-after-write.c 657 test/test-tcp-try-write.c 658 test/test-tcp-write-in-a-row.c 659 test/test-tcp-try-write-error.c 661 test/test-tcp-write-after-connect.c 662 test/test-tcp-write-fail.c 663 test/test-tcp-write-queue-order.c 664 test/test-tcp-write-to-half-open-connection.c
|
H A D | ChangeLog | 296 * test: skip tcp-write-in-a-row on IBM i (Abdirahim Musse) 1126 * kqueue: ignore write-end closed notifications (Jameson Nash) 2575 * unix: loop starvation on successful write complete (jBarz) 2604 * zos: write-protect message queue (jBarz) 3399 * test: fix flaky tcp-write-queue-order (Santiago Gimeno) 3683 * win: add disk read/write count to uv_getrusage (Imran Iqbal) 4185 * stream: retry write on EPROTOTYPE on OSX (Brian White) 4541 * test: enable test-tcp-try-write on windows (Bert Belder) 4887 * test: don't close connection on write error (Trevor Norris) 5908 * test: open stdout fd in write-only mode (Ben Noordhuis) [all …]
|
/libuv/docs/src/guide/ |
H A D | filesystem.rst | 4 Simple filesystem read/write is achieved using the ``uv_fs_*`` functions and the 86 will be triggered after the write is complete*. In our case the callback 87 simply drives the next read. Thus read and write proceed in lockstep via 90 .. rubric:: uvcat/main.c - write callback 100 a write that 'succeeds' may not be committed to disk yet. 121 same patterns as the read/write/open calls, returning the result in the 240 Otherwise ``nread`` is a non-negative number and we can attempt to write that 259 does not get passed through to the write callback trigged on write completion. To 260 get around this we wrap a write request and a buffer in ``write_req_t`` and
|
H A D | basics.rst | 37 **blocking**. The actual write to a hard disk or reading from a network, takes 85 With the basics out of the way, let's write our first libuv program. It does 195 structure that is passed to the callback after the write is done.
|
H A D | processes.rst | 253 read/write buffering to the operating system, so in terms of convenience this 264 read/write flag is from the perspective of the child process. In this case, 354 inter-process communication! Since the master will write the file handle to the
|
H A D | threads.rst | 121 Read-write locks are a more granular access mechanism. Two readers can access 124 holding it. Read-write locks are frequently used in databases. Here is a toy
|
/libuv/src/unix/ |
H A D | signal.c | 133 r = write(uv__signal_lock_pipefd[1], &data, sizeof data); in uv__signal_unlock() 209 r = write(handle->loop->signal_pipefd[1], &msg, sizeof msg); in uv__signal_handler()
|
H A D | async.c | 244 r = write(fd, buf, len);
|
H A D | stream.c | 135 r = write(s->fake_fd, "x", 1); in uv__stream_osx_interrupt_select() 664 return write(fd, vec->iov_base, vec->iov_len); in uv__writev()
|
/libuv/src/win/ |
H A D | req-inl.h | 163 DELEGATE_STREAM_REQ(loop, (uv_write_t*) req, write, handle); in uv__process_reqs()
|
/libuv/.github/workflows/ |
H A D | CI-unix.yml | 91 sudo defaults write /Library/Preferences/com.apple.alf globalstate -int 0
|
/libuv/m4/ |
H A D | libuv-check-flags.m4 | 17 dnl along with this program; if not, write to the Free Software
|