On 14.09.10 00:21, Dave Cridland wrote: > On Tue Jul 13 16:46:00 2010, XMPP Extensions Editor wrote: >> The XMPP Extensions Editor has received a proposal for a new XEP. >> >> Title: XMPP on Mobile Devices >> >> Abstract: This document provides background information for XMPP >> implementors concerned with mobile devices operating in a cellular >> network such as 3G. >> >> URL: http://www.xmpp.org/extensions/inbox/mobile.html >> >> The XMPP Council will decide at its next meeting whether to accept >> this proposal as an official XEP. >> >> > Did I miss some feedback on this? Nope.. You did not. :)
But here some feedback: "Care, however, should be taken not to use XEP-0138 compression when TLS compression is in effect." I think this is already mentioned with a SHOULD NOT in XEP-0138, so I don't see a need to mention it again here. "4. Radio Power" Is there a document we could reference where the levels Idle, FACH, DCH are explained more in detail and their timeout ranges? Just for those who want do go deeper. "5. Conclusions" The conclusions all look reasonable based on the previous elaborations. "6. Notable Extensions" Would be nice to have some example scenario or some rough description of it which shows how those help to increase battery life. I mean it could be quite common for mobile clients to have PEP enabled, frequent and interesting sub-protocols due to update frequency would be User Location and User Tune most likely. Maybe a mention of currently widely present feature, at least in desktop clients, auto-idle messages in presence, would be nice to mention too. Depending on setup they can change quite often. Other than think it's nice to have a document documenting the particulars of using XMPP on 3G (a reference to the relevant standard might be nice here too) networks. Another thing comes to mind when traveling is where you hop through cells into an area where no 3G is available but only GSM is. Would most of the conclusions still be true? Cheers, Tobi -- Tobias Markmann http://ayena.de
smime.p7s
Description: S/MIME Cryptographic Signature
