Comparing version 0.1.2 to 0.1.3
{ | ||
"name": "jqueue", | ||
"version": "0.1.2", | ||
"version": "0.1.3", | ||
"description": "MySQL backed plugable Node.js job queue based on the Beanstalk Job Lifecycle", | ||
@@ -5,0 +5,0 @@ "devDependencies": { |
@@ -1,6 +0,1 @@ | ||
jqueue | ||
====== | ||
Plugable Node.js job queue based on the Beanstalk Job Lifecycle | ||
# Getting Started | ||
@@ -10,11 +5,10 @@ | ||
```javascript | ||
var jqueueClient = require('jqueue'); | ||
var Jqueue = require('jqueue'); | ||
``` | ||
## Init jqueue | ||
## Create jqueue | ||
- dependency: [node-mysql] (https://www.npmjs.com/package/node-mysql) | ||
**Important:** It's necessary call init before call any other method! | ||
```javascript | ||
var jqueueClient = require('jqueue'); | ||
var Jqueue = require('jqueue'); | ||
var db = require('node-mysql'); | ||
@@ -31,9 +25,3 @@ | ||
var jqueue = new jqueueClient.Jqueue(dataSource); | ||
jqueue.init(function(error) { | ||
if(!error) { | ||
console.log('I am alive!'); | ||
} | ||
}); | ||
var jqueue = new Jqueue(dataSource); | ||
``` | ||
@@ -96,12 +84,4 @@ | ||
# Queue | ||
[See Queue Object documentation] (queue) | ||
# Message | ||
[See Message Object documentation] (message) | ||
# Callbacks standard | ||
The callbacks functions need to respect the callback standard (error, data). So, when you set a callback function, make sure that there at least an error parameter. Even if no error occurs, the error parameter needs to be set, but in this case, the error value will be null. |
@@ -36,3 +36,3 @@ var Queue = require('./queue'); | ||
status ENUM(\'ready\', \'reserved\', \'buried\') NOT NULL,\ | ||
data VARCHAR(4096) NOT NULL,\ | ||
data VARCHAR(65535) NOT NULL,\ | ||
priority TINYINT NOT NULL,\ | ||
@@ -39,0 +39,0 @@ date_time TIMESTAMP NOT NULL,\ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
0
54313
85