You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+68-48
Original file line number
Diff line number
Diff line change
@@ -182,8 +182,8 @@ __Tip:__ If the Redis server runs on the same machine as the client consider usi
182
182
| port | 6379 | Port of the Redis server |
183
183
| path | null | The UNIX socket string of the Redis server |
184
184
| url | null | The URL of the Redis server. Format: `[redis:]//[[user][:password@]][host][:port][/db-number][?db=db-number[&password=bar[&option=value]]]` (More info avaliable at [IANA](http://www.iana.org/assignments/uri-schemes/prov/redis)). |
185
-
| parser |hiredis | If hiredis is not installed, automatic fallback to the built-in javascript parser |
186
-
| string_numbers | null | Set to `true`, `node_redis` will return Redis number values as Strings instead of javascript Numbers. Useful if you need to handle big numbers (above `Number.MAX_SAFE_INTEGER === 2^53`). Hiredis is incapable of this behavior, so setting this option to `true` will result in the built-in javascript parser being used no matter the value of the `parser` option. |
185
+
| parser |javascript |__Deprecated__ Use either the built-in JS parser [`javascript`]() or the native [`hiredis`]() parser. __Note__`node_redis` < 2.6 uses hiredis as default if installed. This changed in v.2.6.0.|
186
+
| string_numbers | null | Set to `true`, `node_redis` will return Redis number values as Strings instead of javascript Numbers. Useful if you need to handle big numbers (above `Number.MAX_SAFE_INTEGER === 2^53`). Hiredis is incapable of this behavior, so setting this option to `true` will result in the built-in javascript parser being used no matter the value of the `parser` option. |
187
187
| return_buffers | false | If set to `true`, then all replies will be sent to callbacks as Buffers instead of Strings. |
188
188
| detect_buffers | false | If set to `true`, then replies will be sent to callbacks as Buffers. This option lets you switch between Buffers and Strings on a per-command basis, whereas `return_buffers` applies to every command on a client. __Note__: This doesn't work properly with the pubsub mode. A subscriber has to either always return Strings or Buffers. |
189
189
| socket_keepalive | true | If set to `true`, the keep-alive functionality is enabled on the underlying socket. |
@@ -712,60 +712,80 @@ client.zadd(args, function (err, response) {
712
712
## Performance
713
713
714
714
Much effort has been spent to make `node_redis` as fast as possible for common
715
-
operations. As pipelining happens naturally from shared connections, overall
716
-
efficiency goes up.
717
-
718
-
Here are results of `multi_bench.js` which is similar to `redis-benchmark` from the Redis distribution.
- The JS parser is from now on the new default as it is a lot faster than the hiredis parser
12
+
- This is no BC as there is no changed behavior for the user at all but just a performance improvement. Explicitly requireing the Hiredis parser is still possible.
13
+
- Added name property to all Redis functions (Node.js >= 4.0)
14
+
- Improved stack traces in development and debug mode
15
+
16
+
Bugfixes
17
+
18
+
- Reverted support for `__proto__` (v.2.6.0-2) to prevent and breaking change
19
+
20
+
Deprecations
21
+
22
+
- The `parser` option is deprecated and should be removed. The built-in Javascript parser is a lot faster than the hiredis parser and has more features
23
+
4
24
## v.2.6.0-2 - 29 Apr, 2016
5
25
6
26
Features
7
27
8
-
- Added support for the new `CLIENT REPLY ON|OFF|SKIP` command (Redis v.3.2)
28
+
- Added support for the new [CLIENT REPLY ON|OFF|SKIP](http://redis.io/commands/client-reply) command (Redis v.3.2)
9
29
- Added support for camelCase
10
30
- The Node.js landscape default is to use camelCase. node_redis is a bit out of the box here
11
31
but from now on it is possible to use both, just as you prefer!
12
32
- If there's any documented variable missing as camelCased, please open a issue for it
13
33
- Improve error handling significantly
14
34
- Only emit an error if the error has not already been handled in a callback
15
-
- Emit an error if a command would otherwise silently fail (no callback present)
16
35
- Improved unspecific error messages e.g. "Connection gone from end / close event"
17
36
- Added `args` to command errors to improve identification of the error
18
37
- Added origin to errors if there's e.g. a connection error
0 commit comments