Hi Olle,<br><br>By the looks of things, the Facebook server only sends notifications as HTTP GET and POST, so if you wanted to use RabbitMQ your Facebook callback would be an intermediary that passes messages on to RabbitMQ:<br>
<br><br>(Facebook) ----HTTP---> (Your HTTP server (Apache)) ---Amqp----> (RabbitMQ)<br><br>Thanks,<br>--Robin<br><br><br><br><br><div class="gmail_quote">On Wed, Feb 9, 2011 at 3:06 PM, Olle Jonsson <span dir="ltr"><<a href="mailto:olle.jonsson@gmail.com">olle.jonsson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Would Facebook's <a href="http://developers.facebook.com/docs/api/realtime" target="_blank">Real-time updates</a> be a typical AMQP job?<div>
<br></div><div><a href="https://github.com/facebook/real-time/blob/master/samples/php/callback.php" target="_blank">Sample PHP callback to that API</a><br>
</div><div><br></div><div>My question: Would it be good and AMQP-like to have that <b>callback.php</b> file (aka "the end-point") enqueue messages instead of working on them?</div><div><div><br></div></div><div>
best regards from the sidelines,</div><div> Olle</div>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br>