I would like to thank you for all the hard work you
guys have put into UberMQ. Your ideas and approach
really resonate with me. I like the low thread
counts, the quick response, low latency. I like the
idea of being able to start a server via ant, and at
the same time being able to start one embedded in your
I do have a several questions however. The first
has to do with transactions. I am understand that you
do not support transactions at this time. Is that
correct? If so, do you have any plans to do so in the
immediate future? What methods do you recommend to
get around the lack of transaction support?
Secondly, I would like to be avle to create new Queues
on the fly, instead of having to add one via the admin
tool. Is there an API which would allow an
application to create new queues for an already
running server without requiring a restart?
Third, poking around in your source I understand that I can choose CLIENT_ACK option for connections to destinations. If I interpret the source code correctly, as long as a client does not acknowledge receipt of a message, it will remain in the queue. If this is the case please confirm as I may like to fall back on this feature in order to ensure not losing messages.
Thank you very much for your consideration. I look
forward to your reply.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.