4 ms·
wsgi isnt inherently blocking. it is a protocol and it is up to the implementation on both sides if the interface as to how it is handled. that said, according
by supermatt 5y ago
wsgi isnt inherently blocking. it is a protocol and it is up to the implementation on both sides if the interface as to how it is handled.
that said, according to the docs this seems to be cgi 1.1 which equates to a process per request, which afaik isnt so scalable.
- zozbot234 5y agoWASM "processes" need not be the same as OS-level processes. So I don't think this would have the scalability issues of plain CGI.
- supermatt 5y agointeresting! i will have to have a look into this
- Matthias247 5y agoRight. And the Wasm runtime could run multiple Wasm processes on one OS thread. If one program blocks on stdin/stdput it gets descheduled and the next one can run. Which basically provides the same M:N scheduling that highly scalable Webservers would use.