[Rails] XMPP instead of HTTP
Hey guys.
My friend and I, we are working on iPhone application. This
application uses XMPP protocol to provide chat functionality. Right
now we are designing architecture for the application.
So my friend is working on iPhone side, and I am ruby on rails guy.
My friend suggested, that we wrap every call, that is usually served
via HTTP into XMPP. So, user registration, users search, profile
editing, photo uploading, everything goes via XMPP. No HTTP at all.
My friend wants to use XMPP, because he says, that it's much easier to
implement XMPP on client-side rather HTTP. As for me, this is
bullshit, but we've got a product owner, who have been working with my
friend for a long time and he trusts him.
So what I'm trying to do is to convince my friend and product owner
that using XMPP for what HTTP can work find — is totally not the best
idea.
I feel, that if we implement everything on XMPP, we will have a pain
in an ass till the end of lives. But how do I prove it?
P.S. I'm not against chat over XMPP, I am against users search, photo
uploading, rankings, nearby search and various other restful requests.
Please, leave response. Any help appreciated.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home