Cutlass Developers' Journal

I just wanted to assure people that despite the recent quiet, the project is not dead. I’m in a mode where I’ve been working on features that I’m not going to release until there’s a certain amount of polish there. Expect to see something within the next couple of months. (Licensing and overall project philosophy will be unchanged).

The blog may continue to be quiet until then, however. I’m not quite in a publicity hound kind of mood right now.

as a side note, I did run into some Cutlass users at ToorCon recently, which I was glad to see.

It’s been quiet on the blog recently, partially because there’ve been no new features added for a bit. Instead, it seems like every day is porting day!

We’ve been working on getting the windows port of Cutlass to work, and it seems like we’re only a step away. Of course, I’ve been thinking that for the past week, only to find out that I didn’t know what I didn’t know, so to speak.

I do think we’re getting close, though.

We also hammered out a proposal for the new handshaking protocol this past sunday, which I’ll post shortly.

I’m in Michigan for a wedding this weekend, so it’s been a slow zone for coding. I fixed a couple of bugs in the transport layer that were causing channel leaks (where channels would transmit all their data, but never free up), and I also removed some redundant code in channel initiation.

I also noticed that the new page didn’t have directions as to how to get anonymous subversion access to the latest checkins. Oops. It’s now a link up in the “Download Cutlass” box on the left.

A new code rev is in, 545, which fixes some old bugs with info propogation (Only one connection was getting updates to things like file server status, which was really irking since I’ve added the ability to switch that status on the fly), and new bugs with the directory server.

I’ve also stubbed out some calls for the ALSA module. I ran into two sets of audio problems at Recon, one involving a failure in the ALSA-OSS compatibility layer. Since those bugs are out of my control, I figure I’d better write a native ALSA driver to avoid them.

The other bug I suspect is an instability introduced with some new code in 543 intended to prevent race conditions. I’ll certainly have to fix those before I roll an 0.3 tarball (which I’d like to do, it’s been rather a while).