-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes, this is consistent with some input we received from Aki Niemi of Nokia at XMPP Summit #4 (see section 2.3)...
http://mail.jabber.org/pipermail/standards/2008-February/018036.html On 8/31/09 2:33 PM, Vincent BARAT wrote: > Additional information regarding battery consuption (in favor of XMPP): > according to our tests (using an ammeter), keeping a TCP/IP socket open > DOES NOT CONSUME MORE POWER than having none open at all, as long as > there is no activity on the socket. > > I'm not a cell phone specialist, but I guess it is because keeping it > opened is only a matter of signaling from the phone and tracking from > the backend, then it does not require more power than keeping the phone > "connected" to the GSM network. > > Due to this fact, we at Ubikod are using XMPP instead of HTTP to send > bulk data (logs, event etc.) from cellphones to backends. > > Because the XMPP socket does not have to be reestablished for each set > of data (as opposite to a HTPP REST based service) using XMPP on a long > maintained socket consume less battery than using HTTP if you have to > send data on a regular basis. > > Furthermore, you benefit from the fact that the connection is bi > directional :) Did you say PUSH ? ;-) > > Vincent BARAT a écrit : >> Hello, >> >> TCP/IP connections are stables as long as your 3G or 2G connection is >> not cut. The only thing you need to do is to ensure that your client >> running on the mobile phone reconnect to the XMPP server when the >> connection comes back. >> >> As a developper of the BuddyMob XMPP client on Android, we ave managed >> to keep stable XMPP connections fro several days, even when the user >> moves a lot. >> >> Cheers, >> >> >> Robert Quattlebaum a écrit : >>> Sorry for the bump, but I've been able to keep a stable TCP-based >>> XMPP connection just fine as I move about the SF Bay area. I'm using >>> AT&T. >>> >>> __________________ >>> *Robert Quattlebaum* >>> (Sent from iPhone) >>> >>> On Apr 8, 2009, at 12:31 PM, "Thiranjith ." <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>>> Hi, >>>> >>>> Can we use XMPP to talk to a client on a mobile device (e.g. PDA/ >>>> mobile phone) that is connected to the internet using 3G? From what >>>> I understand, phones' end-point IP changes as they move around, and >>>> generally they are behind the network operator's (At&T, Vodafone >>>> etc) firewall. >>>> >>>> Say that user 'A' sends a message to our mobile client. From what I >>>> understand, the message will go through the XMPP server (e.g. >>>> Jabber.org <http://Jabber.org> or our own) to find where our client >>>> is, so it can route the message. How would the XMPP server know >>>> where to find our client in the place? The IP our client used when >>>> registering with the server could be different now because it could >>>> have moved around. >>>> >>>> Does the mobile client need to periodically notify the server about >>>> its IP? From what I understand, the BOSH technique described in >>>> <http://xmpp.org/extensions/xep-0124.html#intro>http://xmpp.org/extensions/xep-0124.html#intro >>>> is meant to address this, but it seems to work only if the entity >>>> behind the firewall initiate the connection first (in this case, the >>>> client running within the mobile phone). >>>> >>>> Please correct me if I got all this wrong as I am new to XMPP, but I >>>> would greately appreciate if anyone can explain how the xmpp server >>>> finds the mobile client that is on the move. Does our sever needs to >>>> implement that routing logic ourselves? Any articles explaining this >>>> would also be great! >>>> >>>> Thank you! >>>> Thira >>>> >>>> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqcVVMACgkQNL8k5A2w/vyRCgCg3R2R0lfLZn0QS/OOPjYYZt0e Ox0AoOdvfB5IqIauIp4OXaNNY8q3z4MW =Mzi1 -----END PGP SIGNATURE-----
