![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.
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
The npm package rabbitmq-eventemitter receives a total of 0 weekly downloads. As such, rabbitmq-eventemitter popularity was classified as not popular.
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
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.