4 ms·

Huh, interesting. I'd bet that this is a bug. The only other explanation I can think of is that push notifications can take about 3-5 seconds to be delivered a

Huh, interesting. I'd bet that this is a bug. The only other explanation I can think of is that push notifications can take about 3-5 seconds to be delivered as they are routed through Apple's servers. If these are long-poll HTTP requests directly to GroupMe's servers, then the message would be delivered instantaneously.

RandallBrown 15y ago
I filed a bug report with them about it awhile back before I knew what was actually going on. I'd much rather have that short delay than have my phone die after using it. Right now I force kill GroupMe every time I leave it.
- dkasper 15y ago
  It's not only the notification delay. They also do it so that the app doesn't have to reconnect if you reopen it within 10 minutes.
  - eridius 15y ago
    That's a valid reason for using a background task, but it doesn't require constantly polling the server.
kelnos 15y ago
If it's long-polling, why are the requests happening over and over again? It should only need to make a single connection, fire off HTTP headers, and just sit there waiting for chunked-encoded replies. No need to kill the connection and re-establish.