My friend and I are working on an iPhone. This application uses XMPP to provide chat features. We are currently developing the architecture for the application.
So, my friend works on the side of the iPhone, and I'm ruby on the rail.
My friend suggested that we end every call that is usually served through HTTP in XMPP. So, user registration, user search, profile editing, uploading photos, everything goes through XMPP. No HTTP at all.
My friend wants to use XMPP because he says that it is much easier to implement XMPP on the client side, rather than HTTP. As for me, this is crap, but we have a product owner who has been working with my friend for a long time, and he trusts him.
So what I'm trying to do is convince my friend and product owner that using XMPP for what HTTP can work is not a good idea at all.
I feel that if we implement everything on XMPP, we will have pain in the ass for the rest of our lives. But how can I prove it?
PS I do not mind chatting through XMPP, I am against searching for users, uploading photos, ranking, searching nearby and various other quiet requests.
Please leave a response. Any help was appreciated.
Small update:
. , , XMPP HTTP Objective-C. Core Data, . , HTTP-, HTTP- . XMPP, XMPP. , .
, iPhone.
, - ?