computerd publishes Cap'n Web HTTP-batch at /api and Cap'n Web WebSocket at /ws.
Idiomatic Cap'n Web endpoints should place both of these at the same path, preferably /api. There's no need for WebSockets to be served from a different path. The request content (GET with Upgrade vs. POST) unambiguously specifies which the client wants.
(This is a relatively minor thing I noticed while reading the docs. Feel free to ignore me if you prefer.)
computerd publishes Cap'n Web HTTP-batch at
/apiand Cap'n Web WebSocket at/ws.Idiomatic Cap'n Web endpoints should place both of these at the same path, preferably
/api. There's no need for WebSockets to be served from a different path. The request content (GETwithUpgradevs.POST) unambiguously specifies which the client wants.(This is a relatively minor thing I noticed while reading the docs. Feel free to ignore me if you prefer.)