<br>Hi Tony,<br><br>Thanks for your response. Yes, I've been using it for a proof of concept implementation and it works great. Thanks for the great work :) <br><br>Some things that I'm concerned may be a problem in production:<br>
<br>1) The gateway doesn't handle loss of connection to the ejabberd server. I can add code to handle this fairly easily I think.<br><br>2) Consumer Processes are not supervised ( I believe this may be on your To-do list). <br>
If I understand correctly, once a consumer process crashes the user associated with the queue will no longer receive any data. This data would continue to queue up at the server. Even if the user were to go offline and come back online, because of an entry in rabbitmq_consumer_process with queue and pid, a new process will not be created. Am I missing something here? <br>
<br>What would be the best way to make these processes supervised?<br><br>Thanks again,<br>Chetna<br><br><br><div class="gmail_quote">On Tue, Jan 12, 2010 at 9:14 AM, Tony Garnock-Jones <span dir="ltr"><<a href="mailto:tonyg@lshift.net">tonyg@lshift.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">chetna kaur wrote:<br>
> I was wondering if there are any plans of releasing a production ready<br>
> version of the rabbitmq xmpp gateway.<br>
<br>
No, not at the moment. Or at least, the current gateway works well<br>
enough for us to use internally, and I'm told that a number of people<br>
are using it in production, so we don't have a lot of motivation to make<br>
changes to it :-)<br>
<br>
Regards,<br>
<font color="#888888"> �Tony<br>
</font></blockquote></div><br>