Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

worker support? #1

Open
fictorial opened this issue May 17, 2011 · 12 comments
Open

worker support? #1

fictorial opened this issue May 17, 2011 · 12 comments

Comments

@fictorial
Copy link

Are you planning to add support for Node.js based workers?

@smith
Copy link
Contributor

smith commented May 17, 2011

Absolutely. That's the next step after I'm done working on the client. Pull requests are always welcome.

@fictorial
Copy link
Author

ok .. I'll take a look into this.

@smith
Copy link
Contributor

smith commented May 17, 2011

I pushed to a feature branch with a little readme work on a proposed API: 5d34589

I'd like to use the native EventEmitter API as closely as possible, but I haven't quite worked out exactly how to implement things like RESET_ABILITIES with that.

This Issue can stay open until there's a working implementation.

@fictorial
Copy link
Author

I decided it would be fun to write a full Gearman client and worker in CoffeeScript. So I did that today instead of forking your project. Sorry that I was a tease!

@smith
Copy link
Contributor

smith commented May 19, 2011

You're still a tease until you link to the code ;)

I debated using CS originally, and I'm still thinking about a port. It's not too late for a rewrite, and the goal is to have a working node implementation, so the language doesn't matter.

@cjoudrey
Copy link

Any updates on a gearman worker?

Also, the proposed API would not properly work for async jobs.

We should probably have a callback argument which we can call to return the payload.

The callback would be in the form of function(err, data) like other Node callbacks.

For instance, the reverse worker would become:

worker.on("test", function (data, done) {
    done(null, data.toString("utf8").split("").reverse().join(""));
});

Thoughts?

@perezd
Copy link

perezd commented Oct 10, 2011

Any progress on this? Its fairly useless without a worker API.

@cjoudrey
Copy link

@perezd Project seems dead :S

@smith
Copy link
Contributor

smith commented Oct 11, 2011

Project is not dead (or useless IMO.) Just haven't had time to work on it much lately. Sorry, but that's just what's going on.

Pull requests are welcome, and I hope to get around to making updates at some point.

@smith smith closed this as completed Oct 11, 2011
@smith smith reopened this Oct 11, 2011
@aredridel
Copy link

+1 on this from me

@smith
Copy link
Contributor

smith commented Jan 2, 2012

https://github.com/andris9/node-gearman does support workers, though there are no plans on that for some other features: background jobs, priorities, status updates, etc.

@mreinstein
Copy link

Full protocol support for clients and workers https://github.com/mreinstein/node-gearman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants