Refactoring OnStomp
Lately, I’ve been giving some thought to a few issues with the OnStomp gem and how I want to address them. I’ll start by over-explaining the issues, and then wrap up with how I plan to address them.
the two halves of my tasty brain
Lately, I’ve been giving some thought to a few issues with the OnStomp gem and how I want to address them. I’ll start by over-explaining the issues, and then wrap up with how I plan to address them.
So, true to my nature of nothing ever being quite “good enough” I’m already looking to add new features to OnStomp as well as making plans for what version 2.0 will look like.
The OnStomp gem version 1.0.0 has been released. It deprecates my previous Ruby stomp client Stomper.
After a significant re-tooling of Stomper’s IO handling, I’ve got something that seems very fast and very stable, using non-blocking IO.
In working out the particulars of a failover extension to Stomper, I discovered a few subtle but frustrating bugs. As a result, I pushed out 3 versions of the Stomper gem today. This may be the greatest accomplishment of my life.
Every post I make to the stomp-spec group that isn’t a “+1” or “me, too!” is often followed up with a thought of “you’re a moron” about 10 minutes later. I’m going to improve this situation by spending some time hashing out my thoughts here, and if they still look good a couple hours later, then I’ll post them.