title: HTTP Pipelining vs. WebSocket in Boost.Beast advanced server example
body: <p>I have a question to this Boost.Beast example:</p>
  
  <p><a href="https://github.com/boostorg/beast/blob/908f84cb3c023ed7c5bd19e2e5283d3218a6d820/example/advanced/server/advanced_server.cpp" rel="nofollow noreferrer">https://github.com/boostorg/beast/blob/908f84cb3c023ed7c5bd19e2e5283d3218a6d820/example/advanced/server/advanced_server.cpp</a></p>
  
  <p>In line 643 a WebSocket upgrade is done. However, if I understand it correctly, there may still be HTTP write commands in the queue that are asynchronously executed. They are thus executed in parallel to the current WebSocket communication. Is that legal? Or have I not yet fully understood the example?</p>