Closed GoogleCodeExporter closed 8 years ago
Thanks for your input. But what would be the use case? Why do you want to do
this, instead of running GTalkSMS 24/7?
Original comment by fschm...@gmail.com
on 10 Feb 2012 at 1:42
The reason would be to save battery life and mobile data charges. However I now
realise it might use more batter and data to do this than simply keep the
connection alive. Is there any evidence one way or the other?
Original comment by williams...@gmail.com
on 10 Feb 2012 at 1:45
I also think that this would only result in increased battery consumption. Data
charges shouldn't be so excessive, if you use a typical 2 account GTalkSMS
setup, where GTalkSMS has a dedicated account and only 1 contact.
We currently send a tiny keep-alive and test whitespace packet every 15
minutes. Which should not be better then doing a complete login and connection
handshake every 10 minutes. The interval (15min) is currently not configurable,
but I think that 15 minutes is a good trade off, between service availability
and resource consumption.
Original comment by fschm...@gmail.com
on 10 Feb 2012 at 3:47
Original comment by fschm...@gmail.com
on 20 Feb 2012 at 10:59
Original issue reported on code.google.com by
williams...@gmail.com
on 9 Feb 2012 at 7:54