Fabio Forno wrote: > Thanks for the update. Some notes below > > On Sat, Mar 22, 2008 at 1:37 AM, Peter Saint-Andre <[EMAIL PROTECTED]> wrote: > >> 2. XMPP requires a persistent TCP connection, which leads to battery >> drain - as the network connection is required always when client is >> online, the WiFi / GPRS / 3G connection is required as well. The "always >> active" radio transceiver will consume a lot of power and drain the battery. >> >> - OMA IMPS has a solution for this: the client can turn off the >> signalling channel when the client is not in active use (chatting/etc), >> and tell the server to fall back to SMS-based signalling. When the >> server receives new messages that are destined for the client, it will >> inform the client (using a special SMS message) that content is >> available. The client will then resume the network + normal signalling. > >> (PSA NOTE: this is the "session pause" or "session hush" idea...) > > We were talking last week about the same idea with the people at Sapo. > The SMS option is possible also with XMPP since any mobile application > (J2ME, Symbian or the coming Android) can listen for incoming SMSes on > a given port and be automatically scheduled. Besides the session pause > feature,
So do you think that we need to define a generic session pause feature, or is it handled well enough already in BOSH? > with BOSH again it's possible to stop the connection and > re-establish it when we receive an SMS. However this is feature for > carriers, since I don't think that free server operators or users will > pay the cost of an SMS for almost any incoming message. > Unfortunately this is design flaw of GPRS/ 3G networks, and we have > to live with it unless there won't be install battery refills with > fuel cells ;) Heh, yeah. Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
