Thanks for reaching out!
My experience with WebSockets lead me to believe that mixing them with HTTP on the same Netty pipeline would be problematic (although I could be wrong). For example, AWS API gateway has a completely different gateway implementation to handle WebSockets and HTTP requests.
All that being said, it could be argued that a WebSocket-based Netty pipeline could be really handy for browser-based applications! However, I have no experience using Netty for handling WebSockets. My guess is there's a fair amount of tooling for it and my guess is you'd use WebSocket-specific handlers in the Netty pipeline instead of HTTP-specific handlers. For example, in
https://github.com/RestExpress/RestExpress/blob/master/core/src/main/java/org/restexpress/pipeline/PipelineInitializer.java initChannel(SocketChannel ch) method, replacing the 'decoder' and 'encoder' pipeline elements. But I'm only guessing.
There might also need to be different handling of content-type, etc. in the DefaultRequestHandler which is stitched-in in the RestExpress.java class--so maybe a WebSocketRequestHandler.
I haven't looked into handling WebSockets on Netty, but perhaps someone here can be more helpful... :)
Thanks,
--Todd