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

2018-12-19 Thread GitBox
jthomas commented on issue #325: Support for invocations based on websocket 
messages
URL: 
https://github.com/apache/incubator-openwhisk-apigateway/issues/325#issuecomment-448504442
 
 
   More details now available: 
https://aws.amazon.com/blogs/compute/announcing-websocket-apis-in-amazon-api-gateway/


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:
us...@infra.apache.org


With regards,
Apache Git Services


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

2018-11-30 Thread GitBox
jthomas commented on issue #325: Support for invocations based on websocket 
messages
URL: 
https://github.com/apache/incubator-openwhisk-apigateway/issues/325#issuecomment-443140036
 
 
   I can't find any documentation about this feature in AWS at the moment. 
We'll have to wait and see what their implementation looks like. It'll be 
interesting to see how they handle errors and whether they support sending 
messages back outside of the invocation response. 


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:
us...@infra.apache.org


With regards,
Apache Git Services


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

2018-11-01 Thread GitBox
jthomas commented on issue #325: Support for invocations based on websocket 
messages
URL: 
https://github.com/apache/incubator-openwhisk-apigateway/issues/325#issuecomment-435068723
 
 
   > One option would be to define a precise error format 
   
   This seems like the most sensible option. Returning the message with an 
error identifer and message to indicate they need to re-send? 
   
   If we can support both in-bound and out-bound messages this would be a huge 
feature that the other platforms do not support. 


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:
us...@infra.apache.org


With regards,
Apache Git Services


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

2018-10-29 Thread GitBox
jthomas commented on issue #325: Support for invocations based on websocket 
messages
URL: 
https://github.com/apache/incubator-openwhisk-apigateway/issues/325#issuecomment-433982367
 
 
   This would be an excellent feature of the API Gateway . Websocket support 
is something developers ask about a lot... 
   
   - We would need to define the error handling process when the the triggers 
are unavailable or rate-limited. How would we signify to a client that a 
message wasn't delivered?
   
   Another (more difficult) thing to consider is how to make it possible for 
messages to be sent to listening clients outside of responding to an incoming 
event. If we take one of the most common examples for a websocket application, 
a chat application, how could we enable this feature? 
   
   Ideally, an action could call the API Gateway service with a message to pass 
to one or more clients currently connected to pass messages that arrived from 
other sources.


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:
us...@infra.apache.org


With regards,
Apache Git Services