scala - Why is starting a Blaze server that supports websockets different than a server that does not support it in Http4s -


here sample code start blaze server supports websockets in http4s:

https://github.com/http4s/http4s/blob/master/examples/blaze/src/main/scala/com/example/http4s/blaze/blazewebsocketexample.scala#l53

it quite different in case websocket support not required:

https://github.com/http4s/http4s/blob/master/examples/blaze/src/main/scala/com/example/http4s/blaze/blazeexample.scala#l8

why case? possible add withwebsocketsupport on blazebuilder?

i mean, if api can improved, that's great, trying understand how websocket support fits picture because having issues getting web server (that supports websockets) function properly.


Comments

Popular posts from this blog

php - Zend Framework / Skeleton-Application / Composer install issue -

c# - Better 64-bit byte array hash -

python - PyCharm Type error Message -