Hey all,
I just wanted to indicate that I’m planning on a 1.1 release of nanomsg.
This will roll up a number of bug fixes that should improve stability of
inproc (I’ve convinced myself that the inproc thread-safety issues I
thought existed before don’t really exist — long story, but it turns out
that the bugs were in the test code), but there were some real bugs in the
state machines, which I think I’ve ironed out.
It is my intention that this will be the *last* release of libnanomsg.
(That said, as they say, the best laid plans of mice and men…)
The reason for this is that I’m pretty focused, as you may know, on libnng,
which has a compatible API. (In fact, you can just take your nanomsg code,
and link it against libnng directly. :)
libnng isn’t perfect yet, and it isn’t ready for prime time, but it is
getting there, and I really want to focus on that as the way forward — it
has lots of extra capabilities and it should open a lot of new
opportunities.
In the mean time, libnanomsg 1.1 will most likely be released this week.
If you have a favorite bug that you feel *absolutely* needs to be fixed
(and I’ve not already labeled it as a “release stopper”) please let me know
ASAP. I can’t promise I will agree to hold the release for it, but it does
improve the odds if I know the bug is critical to you somehow.
Thanks!
- Garrett
