Question: will gcloud-node support (push) task queues

Like https://cloud.google.com/appengine/docs/python/taskqueue/ ?

I don't see why we couldn't support it. Is there some example of how you would like it to work?

I have a plan to decouple some accessory workers (cpu heavy, with a couple of spawned childrens) from the main nodejs REST server to another dedicated one - removing my async queue and taking advantage of Google's task queues.

I asked specifically about push queues because the main server should push tasks on the queue and the dedicated server should listen to the queue and take care of the task spawing a worker.
I don't think I have specifical examples or requests, as it's the first time I use task queues :)

I use gcloud-node for pretty much every interaction with the google cloud services, so it would be nice to have them supported here, instead of me rewriting square wheels :)

+1

http://stackoverflow.com/questions/29283023/master-slave-pattern-on-google-cloud-using-pub-sub

+1

what about this? you start work on this?
i can help if you need..

We haven't heard anything about this library supporting task queues. Are they only available within App Engine?

https://cloud.google.com/appengine/docs/python/taskqueue/
"Push queues function only within the App Engine environment. These queues are the best choice for applications whose tasks work only with App Engine tools and services. With push queues, you simply configure a queue and add tasks to it. App Engine handles the rest. Push queues are easier to implement, but are restricted to use within App Engine. For more information about push queues and examples of how to use them, see Using Push Queues."

so.. yes

and..

@jgeewax

tagging #917, as this issue relates to that discussion regarding having support for GCE/GAE-specific things in our library

@jgeewax thoughts on this?

Why would you? Pub/Sub is already supported and isn't tied to GAE / doesn't require firing up a GAE instance just to read / write a task.

+1 This would be very for a project that's coming up very soon.

I've added this to our API Implementation Tracker @ #1338 -- this doesn't necessarily mean that we will be supporting this, but we've noted the request and it will be considered amongst the others.