[GitHub] mhamann commented on issue #325: Support for invocations based on websocket messages

[GitBox <gi...@apache.org>]

mhamann commented on issue #325: Support for invocations based on websocket messages
URL: https://github.com/apache/incubator-openwhisk-apigateway/issues/325#issuecomment-434783049
 
 
   @jthomas all very good points.
   
   Since the WebSocket RFC doesn't provide any mechanism by which to supply message headers, I think we might have to implement something custom.
   
   One option would be to define a precise error format (e.g. always JSON with certain properties) that clients must be able to check for and process if something goes wrong.
   
   Another possibility would be to allow the API creator to specify another action / URL that could process an error message and return a message in any format. Even so, something could go wrong with that invocation that would require falling back to the first option.
   
   The chat scenario is interesting as well. A few things have occurred to me as to how we might handle that type of flow, but I'm going to think about it a bit further before writing anything down.
   
   @mdeuser I think there are potentially a number of desirable use cases around this. If the notion of serverless computing is designed to replace many traditional application models, then WebSockets would be integral to the platform.
   
   James already mentioned the chat app example, which would be really cool to duplicate in a serverless context.
   
   Other examples:
   - IoT devices that send a constant stream of telemetry back to an aggregator
   - Collaborative editing (e.g. Google Docs)
   - Real-time stock ticker
   - Gaming

----------------------------------------------------------------
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