![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
redis-wstream
Advanced tools
redis-wstream - node.js redis write stream which streams binary or utf8 data into a redis key using an existing redis client (streams2)
redis-wstream is a node.js redis write stream which streams binary or utf8 data into a redis key using an existing redis client. Tested with mranney/node_redis client. (streams2)
npm install redis-wstream
You will also need the redis
client (npm install redis
) or other compatible library. You an also optionally install hiredis
along with redis
for additional performance.
Construct a write stream instance by passing in client and key to save stream to. Pipe to this instance and when end is emitted, the stream has been saved to redis.
var redis = require('redis');
var redisWStream = require('redis-wstream'); // factory
var client = redis.createClient(); // create client using your options and auth
var d = domain.create();
d.on('error', function (err) {
/* handle error */
})
.run(function () {
readstream // whatever read stream to read from
.pipe(redisWStream(client, 'keyToSaveTo')) // create write stream instance saving to keyToSaveTo
.on('end', function () {
// readstream was successfully saved to redis key: keyToSaveTo
});
});
redisWStream(client, saveKey, [options])
- construct a new write stream using redis client
, saving to the key at saveKey
. Client should not be a normal (non-multi batch) client otherwise it will accumulate the stream in memory before sending. You can provide a batch client as part of options.clientMulti
if you want the final rename to happen as part of another batch.options
can be used to provide additional stream options.options.tempKeySuffix
- can be provided to tell redis what suffix to use for its temporary key which will be used while the stream is being written (which will be renamed to saveKey
when complete). If not provided then a random string will be appended. Note that this needs to be unique so that concurrent writes for same key will not conflict with each other.options.clientMulti
- if provided then once the stream is completely written, the rename operation will be written to this client but not executed, so you can later call exec()
along with any other operations that are par of your transaction. If this option is not provided, then the rename will be performed and executed on the original client. So if you provide this option, you must call options.clientMulti.exec()
yourself at some point after this finishes.Tested with mranney/node_redis client, but should work with any client that implements:
set(key, cb)
append(key, cb)
Note: This module works by appending chunks to a tempKey as the data is streamed in, and then once complete, renames the tempKey to saveKey. In this way the original key is unaffected until the rename happens which is atomic. If options.clientMulti
is provided then the rename will be appended after the stream is done writing and it is up to the user to exec()
the multi client when they are ready for it to occur along with the rest of a batch.
options.clientMulti
)mranney/node_redis does not have direct ability to take a stream and save it to a redis key, so rather than writing this logic again and again, wrap this up into a write stream so we simply pipe to it and it is stored.
Other redis stream implementations use their own direct network connections to redis, but I would prefer to use an existing connection for all my redis work which makes authentication and things lke failover easier to deal with.
If you have input or ideas or would like to get involved, you may:
FAQs
redis-wstream - node.js redis write stream which streams binary or utf8 data into a redis key using an existing redis client (streams2)
The npm package redis-wstream receives a total of 1,451 weekly downloads. As such, redis-wstream popularity was classified as popular.
We found that redis-wstream demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.