
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
rabbitmq-eventemitter
Advanced tools
Simplified rabbitmq events.
npm install rabbitmq-eventemitter
The returned instance exposes a pull
method for receiving and a push
method for sending events.
var rabbitmq = require('rabbitmq-eventemitter');
var queue = rabbitmq('amqp://localhost');
queue.pull('event_name', function(message, callback) {
console.log(message);
callback();
});
queue.push('event_name', 'hello');
Call the provided callback
in push
to acknowledge the message and remove it from the queue. If the callback
is called with an error object as first argument the message is inserted back into the queue.
It's also possible to delay message delivery using the delay
option.
queue.push('event_name', 'hello in 5 seconds', { delay: 5000 });
The namespace
option allows you to control how messages are distributed between consumers. Only one consumer within the same namespace will receive a published message, even though there are others consumers listening on the same event name, this works well for worker queues, where you would have multiple processes receiving messages to be executed. Using different namespaces will on the other hand result in every consumer listening on the same event name to receive the message, which is usefull for a publish-subscribe setup.
var workerQueue_1 = rabbitmq('amqp://localhost', { namespace: 'task-queue' });
var workerQueue_2 = rabbitmq('amqp://localhost', { namespace: 'task-queue' });
var publishQueue = rabbitmq('amqp://localhost'); // namespace not needed when publishing
// Only one of the handlers is called
workerQueue_1.pull('task', function(message, callback) {
console.log(message);
callback();
});
workerQueue_2.pull('task', function(message, callback) {
console.log(message);
callback();
});
publishQueue.push('task', 'work work');
var pubsubQueue_1 = rabbitmq('amqp://localhost', { namespace: 'pubsub-queue-1' });
var pubsubQueue_2 = rabbitmq('amqp://localhost', { namespace: 'pubsub-queue-2' });
var publishQueue = rabbitmq('amqp://localhost'); // namespace not needed when publishing
// Both handlers called.
pubsubQueue_1.pull('task', function(message, callback) {
console.log(message);
callback();
});
pubsubQueue_2.pull('task', function(message, callback) {
console.log(message);
callback();
});
publishQueue.push('task', 'hello all');
If no namespace is provided, it defaults to a random string.
FAQs
Simplified rabbitmq events
We found that rabbitmq-eventemitter demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers 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
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.