2020-10-10 02:43:47 UTC - Rodric Rabbah: I don’t think request/response is dominant in practice but this could very well differ between clouds. The numbers I recall from my days at Ibm had http requests around 40% but this is quite dated now. Some talks from amazon lambda (Chris munns) show api gateway activations were even less compared to asynchronous events. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1602297827054200?thread_ts=1602275511.051100&cid=C3TPCAQG1 ---- 2020-10-10 16:56:30 UTC - Alessandro Banfi: Hi everyone, I'm interested about handle network packets processing using a Serverless approach. To do this, I'm asking you the following: maybe possible trigger one OpenWhisk's action directly from a UDP/TCP socket? In case it is not possible as I think, (as far as I understood, also the solution that permits to use JMS to trigger an action relies on the REST API) , the only two solutions I have in mind are: • incapsulating network datagrams into HTTP requests (with a performance bottleneck) and send them to the API getaway • extending OpenWhisk to trigger one action based on a network datagram received The programming languages I know and I'm currently using are Java and Golang. Do you have any advice for me? https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1602348990055900 ---- 2020-10-10 17:56:43 UTC - Anas: Hi, I'm trying to run Standalone OpenWhisk in docker compose, but when I try to invoke an a hello-world action it takes more than 60 seconds, thus the request fails. Any ideas?
```ok: invoked /_/hello-world, but the request has not yet finished, with id 21767e4b2d714a95b67e4b2d715a9541``` https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1602352603057900 ----
