Pusher integration

[chrismendis]

qmd should publish task progress notifications (if possible) and completion notifications (at the least) to a Pusher channel.

[pkieltyka]

This is a cool idea.. I'd rather see this be generic to any websocket.. and just make that work with Pusher

[dkua]

There really isn't any form of progress notification in qmd right now. We do have the callbacks on Job exit whether it was successful or had encountered an error. I've taken a look at the Pusher docs and it's possible that we could have Pusher as a callback on completion. Script requests could be changed from

{
  "args": [...],
  "callback_url": "callback",
  ...
}

to the following

{
  "args": [...],
  "callback_url": ["callback", "Pusher API callback"],
  ...
}

So have a list of callback_urls to respond to on job completion. The only issue I can see is that all requests to the Pusher API requires authentication. Currently our callback mechanism doesn't deal with that. We'd have to modify qmd to do the following

• accept a list of callback URLs
• have some mechanism to deal with authentication for callbacks

[pkieltyka]

Yea we def don't need this right now

On Jun 17, 2014, at 1:56 PM, David Kua notifications@github.com wrote:

There really isn't any form of progress notification in qmd right now. We do have the callbacks on Job exit whether it was successful or had encountered an error. I've taken a look at the Pusher docs and it's possible that we could have Pusher as a callback on completion. Script requests could be changed from

{ "args": [...], "callback_url": "callback", ... } to the following

{ "args": [...], "callback_url": ["callback", "Pusher API callback"], ... } So have a list of callback_urls to respond to on job completion. The only issue I can see is that all requests to the Pusher API requires authentication. Currently our callback mechanism doesn't deal with that. We'd have to modify qmd to do the following

accept a list of callback URLs have some mechanism to deal with authentication for callbacks — Reply to this email directly or view it on GitHub.