title: Web to rabbitmq - stomp web plugin vs nodejs amqp plugin
body: <p>Im trying to decide if i will connection from web to rabbitmq through:</p>
  <p>Solution 1. Rabbitmq stomp plugin + Rabbitmq web stomp plugin + Sockjs</p>
  <p>Solution 2. Rabbitmq + nodejs through amqp nodejs plugin</p>
  <p>Scenario:</p>
  <p>a) I have one web app that subscribed a queue
  b) I have one java app that is writing to that queue
  c) I have one browser open with solution 1 and another one with solution 2</p>
  <p>I tested both and what happens is that:</p>
  <p>when i send sequential 10.000 messages, the solution 2 is much more quicker than the solution 1. The solution 2 never looses the connection. The solution 1 most of the times looses the connection in a random time (before it gets every message).</p>
  <p>Questions:</p>
  <ol>
  <li><p>Is there any limitation configuration that i can update in solution 1?</p>
  </li>
  <li><p>The problem of the solution 1 is due to: Sockjs? stomp plugin? stomp web plugin? all of them? I don't understand why if i add nodejs in the middle is much quicker than an embedded erlang plugin in rabbitmq (rabbitmq stomp /rabbitmq web stomp plugins).</p>
  <p>note: the stomp plugin or the stomp web plugin never dies. It always continue to listen on their ports.</p>
  </li>
  <li><p>My easy explanation is that the browser cannot process so much sequential messages and nodejs does the manage of this pretty well and the rabbitmq web stomp does not. But is just a guess. Is this correct? If so, how can i solve it?</p>
  </li>
  <li><p>The solution 1 shouldn't be better (in latency too) than the solution 2?</p>
  </li>
  </ol>
  <p>note: If i add in the publisher a difference of 5 milliseconds between the send of each message this problem disappears and the solution 1 performs like solution 2 (for 10.000 messages).</p>
  <p>Thanks for any answer.</p>
  <p>Best Regards,</p>
  <p>Eduardo</p>