Doug Hoyte

Hehe usually a lot smaller but in one case about 500 bytes bigger than that limit, which is how I noticed this :) Outbound messages are sometimes 1M pre-compression and...

Seasocks is an asynchronous server, using the linux-specific epoll() API. There is one thread responsible for managing all events, like reading from the socket, buffering messages, writing to the socket,...

I haven't looked in detail, but I think the thread-per-listener approach is probably your best option. Hooking into the event loop isn't very easy (ie requires code modification) as we...

I implemented the compression for websockets. For my applications it has never seemed necessary to compress page handlers. First, because I rarely use them, and second because a reverse proxy...

@szdytom - You're lucky, the job is available. Wiki is here: https://github.com/mattgodbolt/seasocks/wiki/Seasocks-quick-tutorial

Personally I would consider if it's possible for your application to use a server that specialises in file serving (nginx is good) because it can probably do it much more...

I just realised my comment may have come off sounding discouraging, sorry for that. I actually do think this is a worthwhile patch! Also, this was just my opinion and...

I don't know, I ended up using a different library: https://www.npmjs.com/package/react-compound-slider

Hey guys, the v0.14 branch of uWebSockets has websocket client support, so using the older version might be your best bet if you need a client. It's way better than...

The 0.14 API works well for me. I haven't really considered how the HTTP client features will interact with websockets, but purely thinking about websockets, here's a quick sketch of...