Well it felt like it took me forever to get this all put together but I finally have a release candidate for ActiveMQ-CPP 3.0. The first candidate RC0 can be downloaded from the Apache ActiveMQ-CPP website here.
I've tested the release on Fedora 10 and Windows XP both in 32bit and 64bit compiles. Now I need some users to grab it and start testing it out to find the bugs I didn't.
Monday, April 20, 2009
Thursday, April 16, 2009
ActiveMQ-CPP Release Candidte
I've been trying all week to get the CPP client to build cleanly on Windows but still haven't been able to resolve all the DLL build issues, and don't even get me started on 64bit builds. Why is building on Windows always such a pain in the arse?
In the meantime I've resolved a couple of issues that were submitted last week that fix some pretty important things. We had previously written some code to hand sending the C++ strings to the Java broker in the native Modified UTF-8 format that Java uses but we made a mistake and didn't properly encode NULLs or any ASCII character over 127, well that now all fixed. As a bonus I realized that our code was also not taking advantage of the fact that the Openwire processing on the Java side allows for strings to be encoded with a size larger than 65535 bytes for string values in the Message properties not just in the TextMessage payload, so the long standing limit on string length in Message properties is now gone as well.
One other small fix adds the ability to set the max inactivity duration value on the URI and to properly negotiate it with the broker.
So all in all not a bad week as far as improvements to the client goes, now if only this Windows build would finish...
In the meantime I've resolved a couple of issues that were submitted last week that fix some pretty important things. We had previously written some code to hand sending the C++ strings to the Java broker in the native Modified UTF-8 format that Java uses but we made a mistake and didn't properly encode NULLs or any ASCII character over 127, well that now all fixed. As a bonus I realized that our code was also not taking advantage of the fact that the Openwire processing on the Java side allows for strings to be encoded with a size larger than 65535 bytes for string values in the Message properties not just in the TextMessage payload, so the long standing limit on string length in Message properties is now gone as well.
One other small fix adds the ability to set the max inactivity duration value on the URI and to properly negotiate it with the broker.
So all in all not a bad week as far as improvements to the client goes, now if only this Windows build would finish...
Thursday, April 2, 2009
ActiveMQ-CPP 3.0 Right around the corner
There's been a lot of work going on to revamp ActiveMQ-CPP over the past couple of months. The major new feature of course if Failver support, but besides that there's also been a lot of work done to make the code faster and more reliable. The end is in sight, Failover is working now, and most of the open issues are closed. There are a few small tasks remaining as well as a lot of testing to do but the code is now at a point where folks can start using it. I just finished making several fixes to the Transactions handling code and also cleaned up the way Message's are ack'd. If all goes well in my testing I'm hoping to have a release candidate out in another week or so.
Saturday, February 28, 2009
Writing a CMS User Guide
I decided that the CMS page was decidedly lacking in actual documentation on how to use CMS so I've started putting together a user guide / overview of CMS and the ActiveMQ-CPP implementation of CMS. There's not a lot there yet to review, but as always contributions are welcome.
Here's the link.
http://activemq.apache.org/cms/cms-api-overview.html
Here's the link.
http://activemq.apache.org/cms/cms-api-overview.html
Wednesday, January 14, 2009
What's ahead for ActiveMQ-CPP
ActiveMQ-CPP started out as a Stomp based client for AMQ a couple years ago, since then its grown and evolved to support the native OpenWire protocol used in AMQ along with a slew of other features. Unfortunately its reached a point where the architure that we originally came up with is working against adding new features like Failover support for example. That's why I'm now focusing on a major refactor of the code to correct some of the shortcomings that are standing in the way of new features and also to improve performance and hopefully reliability at the same time.
From this point ou the 2.x branch will only see releases when there's a compelling reason to do so such as a critical fix or other small tweaks that helps someone currently using the library.
The next major release will be version 3.0. What we gain from this will be a much cleaner architecture and hopefully much faster adoption of new features that bring the C++ client closer to feature parity with the Java client. The main new feature targeted for 3.0 is failover support, but hopefully we'll be able to sneak in a few other goodies as well.
Stay Tuned.
From this point ou the 2.x branch will only see releases when there's a compelling reason to do so such as a critical fix or other small tweaks that helps someone currently using the library.
The next major release will be version 3.0. What we gain from this will be a much cleaner architecture and hopefully much faster adoption of new features that bring the C++ client closer to feature parity with the Java client. The main new feature targeted for 3.0 is failover support, but hopefully we'll be able to sneak in a few other goodies as well.
Stay Tuned.
Friday, November 14, 2008
Offically Part of the FUSE Team
I'm now working for Progres Software on the FUSE Open Source team. This means I'm able to work full time on Projects like ActiveMQ-CPP which is soon to part of the FUSE product.
Wednesday, November 5, 2008
ActiveMQ-CPP
You can check out my Open Source project ActiveMQ-CPP here: http://activemq.apache.org/cms/
Subscribe to:
Posts (Atom)