fastwebsockets

Improves memory efficiency and reduces CPU overhead in the WebSocket writing and fragment processing logic. Shifted to ownership transfers and in-place mutations and reduced the number of heap allocations and eliminate unnecessary buffer zero-initializations. Operation After this PR Write Header Allocation + Copy Decode Text $O(1)$ Ownership transfer / Truncate

Hi! I’m trying to eliminate memory allocations when using my websocket handler, but read_frame currently allocates a new Vec for (almost) every incoming frame. Would it be possible to provide an API variant that lets users supply a buffer to read into, avoiding these allocations? Or do you know of any workaround for this issue?