<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 02/03/11 8:15 PM, Matthew Sackman wrote:
<blockquote cite="mid:20110302144539.GA31527@rabbitmq.com"
type="cite">
<pre wrap="">Understood. A lot of our development is driven by user needs, so if
there are things you think are missing then please let us know and we
may adjust things as necessary. This flexibility is indeed one of the
reasons why we don't have a firm published roadmap</pre>
</blockquote>
<br>
On the same page, I am using RabbitMQ for communication between apps
right now and it's performance is awesome.<br>
<br>
The features that I am missing currently for use in my future apps
are :<br>
<ul>
<li>Easier way to do Queue Replication (with messages). DRBD and
heartbeat is not the solution I watn to use. It would be better
to have an application level replication (similar to RabbitMQ
clustering).</li>
<li>Messages reappearing in queue after No-ACKs in a set time out.
(client should not be made to hold a connection (and channel) to
do the same).</li>
<li>A better push model to push messages to clients (looking at
Java). The current Consumer model I feel needs to improve for
handling connection terminations.</li>
</ul>
Please let me know if any of these are being worked on currently or
are demands of other users.<br>
<br>
PS: I do not care about the AMQP protocol much and want a message
queue engine more suited to my use case. So this might be the cause
of any of my feature requests not in line with the specification(my
ignorance, please forgive).<br>
<br>
-Thanks a ton.<br>
Abhishek Kona
</body>
</html>