Nothing bad, a Mummy server won't even notice. No worker thread ever waits on socket IO (neither reading or writing) and this is an important part of Mummy's design. The IO thread that uses epoll / etc will just slowly eat the bytes with essentially 0 load on the server in the same fundamental way async would.
- Show Nim: Mummy, a new HTTP + WebSocket server that return... guzba
- Show Nim: Mummy, a new HTTP + WebSocket server that r... ducdetronquito
- Show Nim: Mummy, a new HTTP + WebSocket server th... guzba
- Show Nim: Mummy, a new HTTP + WebSocket serve... sekao
- Show Nim: Mummy, a new HTTP + WebSocket s... guzba
- Show Nim: Mummy, a new HTTP + WebSoc... Araq
- Show Nim: Mummy, a new HTTP + We... elcritch
- Show Nim: Mummy, a new HTTP ... guzba
- Show Nim: Mummy, a new HTTP ... jasonfi
- Show Nim: Mummy, a new HTTP ... boia01
- Show Nim: Mummy, a new HTTP ... alexeypetrushin
