You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm writing and HTTPS server with WSS support. I've noticed that it's extremely slow to compile and generates a very bloated binary.
I've tried #including only what I need from both Asio and Beast but that makes no difference.
HTTPS on its own is fine. HTTP + WS is fine. But HTTPS + WSS is mega slow to compile (like 30s to compile a single file)
Anybody noticed this before? @vinniefalco what's the state of https://github.com/cppalliance/http_proto and https://github.com/cppalliance/ws_proto ?
I imagine you eventually want to replace Beast with your suite of "sans-io" libraries that sit on top of Asio right?
The text was updated successfully, but these errors were encountered:
I'm writing and HTTPS server with WSS support. I've noticed that it's extremely slow to compile and generates a very bloated binary.
I've tried #including only what I need from both Asio and Beast but that makes no difference.
HTTPS on its own is fine. HTTP + WS is fine. But HTTPS + WSS is mega slow to compile (like 30s to compile a single file)
Anybody noticed this before?
@vinniefalco what's the state of https://github.com/cppalliance/http_proto and https://github.com/cppalliance/ws_proto ?
I imagine you eventually want to replace Beast with your suite of "sans-io" libraries that sit on top of Asio right?
The text was updated successfully, but these errors were encountered: