Pavel, -The specific point your friend made is arguable -The basic principle of sticking to one communication mechanism is good -I guess this is an architectural decision point and there are implications that choice.
The questions that would run through my head are: -Is the application a "real-time" app (I certainly am not talking hard realtime) -Is Voice and Video a big part of the iPhone app? -Is the architecture proposed a standard Jingle/P2P architecture for your application? (i.e. Jingle extension for XMPP, or XEP-0166) -Is there a plan to use XMPP friendly infrastructure at the backend like the Google App Engine at the back? Or are you going to spin your own? -Do there a desire to/need to interoperate with, say, Google talk? (Google Talk is Jingle-like) I also know Apple is Jingle friendly (Re: http://xmppjingle.blogspot.com/2009/10/jingle-on-iphone-over-3g-and-apples.html) My suggestion for you is to go through this resource (apologies in advance if you already have) so you have a much better picture when proposing a RESTful HTTP alternative: http://oreilly.com/catalog/9780596521271/ which has its own pros and cons. All the best! sincerely, keshava ----- Original Message ----- From: [email protected] To: [email protected] Sent: Tuesday, December 28, 2010 11:22:28 AM GMT -08:00 US/Canada Pacific Subject: Re: XMPP instead of HTTP Out application is a p2p chat. We decided to use XMPP for chat, that's ok. But also we need to send various requests to the server (say, receive top100 users or search nearby users or rank someone or leave a comment to profile or upload a photo). So, there's lots of stuff to process it on server. And the question is — should we use XMPP to perform such generic requests (which usually goes through simple HTTP)? Here's what my iPhone friend told me, who wants to use XMPP instead of HTTP. it's quiete hard to receive response from both XMPP and HTTP in Objective-C. Because every single object and its data should be stored in Core Data model, while this model can't be securely modified from various places. Say, if you use HTTP transport, you always want to use only HTTP transport to update data in your model. And if you use XMPP, you should always use XMPP. So, you can't use both. It sounds weird for me, can anyone explain me that, please? On Dec 27, 4:28 pm, Keshava Rangarajan <[email protected]> wrote: > Hi Pavel, > -Interestingly, Roy Fielding had a post on this topic a few years > ago..(http://roy.gbiv.com/untangled/2008/paper-tigers-and-hidden-dragons) > -Im not sure about the nature/type of the application you guys are building > -If your application a peer to peer app WITHOUT any need for any centralized > services that provide access to global/combined state (e.g. a centralized > registry of all users, their profiles etc.) then XMPP would work(e.g. p2p > chat & p2p data services) > -For most other cases, restful http should suffice if designed properly. > > sincerely, > keshava > > > > > > > > ----- Original Message ----- > From: [email protected] > To: [email protected] > Sent: Monday, December 27, 2010 3:40:03 PM GMT -08:00 US/Canada Pacific > Subject: 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 > "iPhoneWebDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/iphonewebdev?hl=en. -- You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en. -- You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en.
