>You don't need AMQP on your client side at all based upon your<br>
>descriptions. You already have a methodology for contacting a server<br>
>(the socket connection described). The only role for AMQP would be on<br>
>the server side.<br>
<br>I am not sure how you got that impression. I am not using AMQP on the client side. I never mentioned it like that. iPhone is the client. AMQP (RabbitMQ) is installed in our server. <br><br>>I think you might be trying to squeeze AMQP (and rabbit) into a place<br>
>where it doesn't fit.<br>
>Why don't you try describing your entire messaging architecture for<br>
>us. Perhaps we can suggest improvements.<br><br>Here it is...<br><br>iPhone app -> socket server -> RabbitMQ server<br><br>iPhone app has some social networking features in addition to the chat component. Think of it like mini-facebook inside iPhone. When a user types a message inside chat window of iPhone app, the message travels to Socket server which directs the message depending on what is on the message header. If the message header says "this message is for RabbitMQ", socket server will route to RabbitMQ. When a message comes from RabbitMQ to socket server, it should have message header that says "Route this to xxxxxx user". Then, socket server will route the message to appropriate user(s).<br>
<br>It all looks good, but it doesn't work. Because I don't know how to make a call to RabbitMQ using the message from socket server and how to pass the message from RabbitMQ to socket server in binary format. <br>
<br>Thanks.<br><br><br><div class="gmail_quote">On Mon, Sep 14, 2009 at 8:11 PM, Chuck Remes <span dir="ltr"><<a href="mailto:cremes.devlist@mac.com">cremes.devlist@mac.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;">
<div class="im"><br>
On Sep 14, 2009, at 8:09 PM, Alex Gentle wrote:<br>
<br>
> >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<br>
> binary data. But, this binary data can't be interpreted by RabbitMQ<br>
> unless I put another middle layer to translate this into call to<br>
> RabbitMQ.<br>
><br>
> >I don't know how the network event notification works in iPhone OS<br>
> 3.x<br>
> >(i.e. I don't know whether you get it to pre-empt the phone's<br>
> kernel).<br>
><br>
> Actually it's not related to iPhone. I was mentioning about polling<br>
> mechanism in RabbitMQ. Meaning that, RabbitMQ doesn't inform the<br>
> user when he gets the message. User has to check every few seconds<br>
> to see if there is anything in his queue. So, iPhone app (OR any<br>
> application for that matter) needs to constantly check RabbitMQ to<br>
> see if there is any message. That's going to cost lot of bandwidth<br>
> when I port the app to mobile devices.<br>
><br>
> Thank you for all the answers.<br>
<br>
</div>You don't need AMQP on your client side at all based upon your<br>
descriptions. You already have a methodology for contacting a server<br>
(the socket connection described). The only role for AMQP would be on<br>
the server side.<br>
<br>
I think you might be trying to squeeze AMQP (and rabbit) into a place<br>
where it doesn't fit.<br>
<br>
Why don't you try describing your entire messaging architecture for<br>
us. Perhaps we can suggest improvements.<br>
<br>
cr<br>
<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br>