>Alex, you haven't explained why your app can only send a specific<br>
>binary stream to a socket - for intents and purposes AMQP is no more<br>
>than a *stream* of binary data.<br>
<br>I am not sure. It's not a specific binary stream, it can be any binary data. But, this binary data can't be interpreted by RabbitMQ unless I put another middle layer to translate this into call to RabbitMQ. <br>
<br>>I don't know how the network event notification works in iPhone OS 3.x<br>
>(i.e. I don't know whether you get it to pre-empt the phone's kernel).<br><br>Actually it's not related to iPhone. I was mentioning about polling mechanism in RabbitMQ. Meaning that, RabbitMQ doesn't inform the user when he gets the message. User has to check every few seconds to see if there is anything in his queue. So, iPhone app (OR any application for that matter) needs to constantly check RabbitMQ to see if there is any message. That's going to cost lot of bandwidth when I port the app to mobile devices.<br>
<br>Thank you for all the answers.<br>
<font color="#888888"><br></font><br><br><br><br><div class="gmail_quote">On Mon, Sep 14, 2009 at 4:12 PM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</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;">
Alex,<br>
<div class="im"><br>
On Mon, Sep 14, 2009 at 8:15 PM, Alex Gentle <<a href="mailto:alexgentle@sify.com">alexgentle@sify.com</a>> wrote:<br>
> Ben, Socket server is just relaying data back and forth. It's essential to<br>
> use socket server, because of the way entire application is set up. My<br>
> iPhone app has chat inside in addition to couple of other photo sharing<br>
> features. The idea is to use RabbitMq for iPhone chat app�to send/receive<br>
> messages.<br>
><br>
> Because the socket server accepts only binary data, I am not sure how do I<br>
> send/receive messages to RabbitMQ server. Without socket server in the<br>
> picture, it works like a charm, iPhone can send message to RabbitMQ and<br>
> receive the responses. But, due to the constraints I have, the message has<br>
> to go thru socket server.<br>
<br>
</div>Alex, you haven't explained why your app can only send a specific<br>
binary stream to a socket - for intents and purposes AMQP is no more<br>
than a *stream* of binary data.<br>
<div class="im"><br>
> another possible problem is that iPhone app has to keep on checking RabbitMQ<br>
> for any messages available. This will be a real problem, if I port iPhone<br>
> app into a mobile app because of bandwidth it's going to consume.<br>
<br>
</div>I don't know how the network event notification works in iPhone OS 3.x<br>
(i.e. I don't know whether you get it to pre-empt the phone's kernel).<br>
<font color="#888888"><br>
Ben<br>
</font></blockquote></div><br>