libwebsock / Blog: Recent posts

It has been about a week since I've updated. I'm currently working on rewriting the core of libwebsock. At the moment, a single event loop sits in the main application thread handling all incoming and outgoing data. I've made some heavy modifications, including the addition of worker threads and a worker queue / management system. Each new connection will spawn a new event base within its own thread that waits and listens for events on each clients socket file descriptor. This is to combat the fact that libwebsock initially only has a single event base sitting in the back end. I've changed this as of now and it appears to be working well. I should have an updated version released within the next few days that improves not only performance, but stability as well. Stay tuned, she's coming along. I'm just slow and have a million other things on my plate right now as well.

I just got the new API documentation up. I still have a little more work to do on it, but it should serve as enough to get people started for right now.

I've spent a good bit of time working on libwebsock and implementing a few new features and bug fixes. I've also spent a portion of that time working on some of the upcoming features on a second branch. I've brought the version down to pre-1.0.0 in order to convey that it's really not fully production ready right now. It's fast, it's hella stable - but it leaks memory. I need to go back and free memory once finished up with it. That's on the agenda and will be done before 1.0.0 is officially released.