You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/04/17 20:50:55 UTC

[GitHub] csantanapr opened a new issue #3558: WebTrigger (WebAction async)

csantanapr opened a new issue #3558: WebTrigger (WebAction async)
URL: https://github.com/apache/incubator-openwhisk/issues/3558
 
 
   So far in multiple occasions have talk to customers/users using OpenWhisk that they have a need to call a Web Action but want the Action to return right away but continue to do business logic.
   
   One tangible use case is Web Analytics:
   Web sites will call a web url on APIGateway, they would get back 202 response right away with the activation id of the web action.
   The action will process the http request, taking more time (i.e. 1 second). The web site doesn't have to wait 1 second for it.
   
   The current way of achieving is not optimal and I see a lot of folks copy pasting the same solution.
   Were the web action will invoke another action that does the real work in async for example using the npm package "openwhisk" and then returning 202 with the activation id back to web client.
   For every call it would generate 2 action invocations and user might reach concurrent or minuteRate limits, in addition creating activation records for web actions that don't do much just schedule an action.
   
   The proposal is to have a url for the web action that the controller will return right away with 202 and the activation id back to web client, and schedule the web action to run async.
   Web Action url sync => `https://${APIHOST}/api/v1/web/guest/demo/hello`
   Web Trigger url async => `https://${APIHOST}/api/v1/web/trigger/guest/demo/hello`
   
   This might sound like a Web Hook, but I think Web Hook have a bit more complexity and a Web Hook I would say is an implementation using the Web Action sync url.
   Ref: https://webhooks.pbworks.com/w/page/13385124/FrontPage
    

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services