lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
isaacs	223f22a30d	blog: Post about 0.11.1	12 years ago
isaacs	56e90dacb3	blog: Post about 0.10.4	12 years ago
Sean Silva	63466e5cae	doc: document value of `this` inside listeners Fixes #5326.	12 years ago
Ben Noordhuis	a835a2fc47	website: add link to nightlies on download page	12 years ago
Kelly Gerber	36503b523d	docs: update path.join() example for v0.10 The current example shows the behavior of v0.8. In v0.10 arguments to path.join() must be strings; otherwise, an exception is thrown.	12 years ago
Ryan Graham	b02b93b2a2	doc: note a gotcha with http.Server sockets	12 years ago
isaacs	b0de1e4a41	stream: Fix unshift() race conditions Fix #5272 The consumption of a readable stream is a dance with 3 partners. 1. The specific stream Author (A) 2. The Stream Base class (B), and 3. The Consumer of the stream (C) When B calls the _read() method that A implements, it sets a 'reading' flag, so that parallel calls to _read() can be avoided. When A calls stream.push(), B knows that it's safe to start calling _read() again. If the consumer C is some kind of parser that wants in some cases to pass the source stream off to some other party, but not before "putting back" some bit of previously consumed data (as in the case of Node's websocket http upgrade implementation). So, stream.unshift() will generally never be called by A, but only called by C. Prior to this patch, stream.unshift() also unset the state.reading flag, meaning that C could indicate the end of a read, and B would dutifully fire off another _read() call to A. This is inappropriate. In the case of fs streams, and other variably-laggy streams that don't tolerate overlapped _read() calls, this causes big problems. Also, calling stream.shift() after the 'end' event did not raise any kind of error, but would cause very strange behavior indeed. Calling it after the EOF chunk was seen, but before the 'end' event was fired would also cause weird behavior, and could lead to data being lost, since it would not emit another 'readable' event. This change makes it so that: 1. stream.unshift() does not set state.reading = false 2. stream.unshift() is allowed up until the 'end' event. 3. unshifting onto a EOF-encountered and zero-length (but not yet end-emitted) stream will defer the 'end' event until the new data is consumed. 4. pushing onto a EOF-encountered stream is now an error. So, if you read(), you have that single tick to safely unshift() data back into the stream, even if the null chunk was pushed, and the length was 0.	12 years ago
isaacs	50be39792a	blog: Fix title for v0.8.23 release	12 years ago
isaacs	67096fdb38	blog: Post for v0.8.23	12 years ago
Rod Vagg	ccabd4a6fa	process: expose NODE_MODULE_VERSION in process.versions	12 years ago
Ben Noordhuis	e8c01739cd	doc: document linux pwrite() bug On Linux, positional writes don't work when the file is opened in append mode. The kernel ignores the position argument and always appends the data to the end of the file. To quote the man page: POSIX requires that opening a file with the O_APPEND flag should have no affect on the location at which pwrite() writes data. However, on Linux, if a file is opened with O_APPEND, pwrite() appends data to the end of the file, regardless of the value of offset.	12 years ago
isaacs	aeef9518c6	doc: Correct caveats for http Readables	12 years ago
isaacs	0f460b03f3	blog: Post about 0.10.3	12 years ago
Michael Hart	440dcae987	Ensure BAD domain example actually uses domain	12 years ago
isaacs	1d17ced200	blog: v0.11.0 release	12 years ago
isaacs	f1fa756681	blog: Update linux binary tarball shasums I just accidentally the binary release.	12 years ago
isaacs	708e8589ea	blog: Post about v0.10.2	12 years ago
isaacs	5ae26f3750	doc: Add 'don't ignore errors' section to domain Also, an example program of using cluster and domain to handle errors safely, with zero downtime, using process isolation.	12 years ago
Benjamin Ruston	024a8b0cb4	doc: debugger, dns, http: fix grammar	12 years ago
Benjamin Ruston	372911ffc7	doc: addon: fix grammar	12 years ago
Ben Noordhuis	a80a132b38	doc: child_process: document 'error' event Fixes #5130.	12 years ago
Ben Noordhuis	0e08e147c7	doc: fix formatting in tty.markdown Fixes #5135.	12 years ago
Ben Noordhuis	cfd0dca9ae	crypto: make getCiphers() return non-SSL ciphers Commit `f53441a` added crypto.getCiphers() as a function that returns the names of SSL ciphers. Commit `14a6c4e` then added crypto.getHashes(), which returns the names of digest algorithms, but that creates a subtle inconsistency: the return values of crypto.getHashes() are valid arguments to crypto.createHash() but that is not true for crypto.getCiphers() - the returned values are only valid for SSL/TLS functions. Rectify that by adding tls.getCiphers() and making crypto.getCiphers() return proper cipher names.	12 years ago
Mathias Bynens	488b74d68b	doc: mention `process.*.isTTY` under `process`	12 years ago
Ben Noordhuis	132c77e9f9	doc: document that stdio is usually blocking	12 years ago
isaacs	92cc187881	blog: Post for v0.10.1	12 years ago
Iskren Ivov Chernev	2f4a62c5e1	doc: fix streams2 SimpleProtocol example A non-existing variable `b` was used to queue data for reading.	12 years ago
Ben Noordhuis	808b7ada07	doc: fix broken links in blog footer The blog lives at blog.nodejs.org while the main website lives at nodejs.org. Ergo, use absolute URLs for links to the main website. Fixes #5062.	12 years ago
JeongHoon Byun	f217b5ed62	doc: fix typo in crypto docs	12 years ago
Yi EungJun	852444a720	doc: https: Fix the link to tls.connect	12 years ago
koichik	1f53cfdeae	doc: don't mark fs callbacks as optional Refs #5005, #5008	12 years ago
Adam Malcontenti-Wilson	028c630ecd	doc: change dgram to socket for properties of dgram.Socket Fixes #4919.	12 years ago
Ben Noordhuis	fa05e8a270	doc: implicit fs callbacks don't throw in v0.10 But they will in v0.12. Re #5005.	12 years ago
Ben Noordhuis	7b7235a232	doc: add note on process.title max length Fixes #5006.	12 years ago
Ben Noordhuis	9af0085f70	doc: path.join() arguments must be strings In v0.8, non-string arguments were ignored. v0.10 throws an exception.	12 years ago
isaacs	7a07b31a2f	blog: Fix typo in typo fix	12 years ago
Nathan Rajlich	598b5e4593	blog: fix small typo in v0.10.0 release article	12 years ago
Ben Noordhuis	da10bb85ff	doc: events: add 'removeListener' event section Amends commit `84221fd` by (also) documenting the 'removeListener' event in a dedicated section, like the 'newListener' event. Fixes #4977.	12 years ago
isaacs	228ad9357c	blog: Post about v0.10.0	12 years ago
isaacs	b3cbb16f41	zlib: Manage flush flags appropriately If you call z.flush();z.write('foo'); then it would try to write 'foo' before the flush was done, triggering an assertion in the zlib binding. Closes #4950	12 years ago
Ben Noordhuis	96a314b68b	buffer: strip high bits when converting to ascii Consider the following example: console.log(Buffer('ú').toString('ascii')); Before this commit, the contents of the buffer was used as-is and hence it prints 'ú'. Now, it prints 'C:'. Perhaps not much of an improvement but it conforms to what the documentation says it does: strip off the high bits. Fixes #4371.	12 years ago
Andreas Madsen	bdf7ac2c5d	child_process: support sending dgram socket child.send can send net servers and sockets. Now that we have support for dgram clusters this functionality should be extended to include dgram sockets.	12 years ago
Ben Noordhuis	71694361f9	doc: dgram: add v0.10 bind() behavior note dgram.Socket#bind() is always asynchronous now. Add a note at the top of the documentation that explains how to upgrade. Fixes #4944.	12 years ago
Ben Noordhuis	924f603e26	doc: dgram: document bind() callback argument	12 years ago
isaacs	9c5812574f	blog: Post for v0.8.22	12 years ago
isaacs	277a2545d2	blog: Update streams2 feature post to match actual doc	12 years ago
isaacs	116d6c4402	blog: Post for 0.9.12	12 years ago
isaacs	d258fb0212	http: More useful setTimeout API on server This adds the following to HTTP: * server.setTimeout(msecs, callback) Sets all new connections to time out after the specified time, at which point it emits 'timeout' on the server, passing the socket as an argument. In this way, timeouts can be handled in one place consistently. * req.setTimeout(), res.setTimeout() Essentially an alias to req/res.socket.setTimeout(), but without having to delve into a "buried" object. Adds a listener on the req/res object, but not on the socket. * server.timeout Number of milliseconds before incoming connections time out. (Default=1000602, as before.) Furthermore, if the user sets up their own timeout listener on either the server, the request, or the response, then the default behavior (destroying the socket) is suppressed. Fix #3460	12 years ago
isaacs	b0f6789a78	stream: Remove bufferSize option Now that highWaterMark increases when there are large reads, this greatly reduces the number of calls necessary to _read(size), assuming that _read actually respects the size argument.	12 years ago
isaacs	5038f40185	node: Add --throw-deprecation Extremely handy when tracking down a flood of recursive nextTick warnings.	12 years ago

1 2 3 4 5 ...

1481 Commits (223f22a30d097e1c878d14cf666858e3bb3046c9)