2 ms·

are you using both websocket and your new protocol ? what is the different usecases for each ? also, did you measure power consumption on platforms like androi

are you using both websocket and your new protocol ? what is the different usecases for each ? also, did you measure power consumption on platforms like android ? one of the big problems with a lot of protocols is the impact of power consumption. I will tradeoff 5 seconds of latency if it reduces power consumption by 50% on my phone. Actually - this is one of the questions that I have: which library should an ordinary app use to have decent power consumption performance for a messaging platform. Fast response and realtime is not a criteria. Websockets, XMPP, long polling ?

ex3ndr 11y ago
> are you using both websocket and your new protocol ? what is the different usecases for each ? Yes. We use at lowest layers websocket and TCP just for transmitting binary frames. Our protocol is very complicated for providing stable cnnections. > also, did you measure power consumption on platforms like android ? This is not how cellular data works. It warms up radio before any active transmit and it lasts for much more that 5 seconds after last byte was sent. This doesn't help you at all. We have small problems in our clients with power consumption, but this is in application level, not networking. > Actually - this is one of the questions that I have: which library should an ordinary app use to have decent power consumption performance for a messaging platform. In all cases it depends how you use them in application level.