Details
-
Type: New Feature
-
Status: Resolved
-
Priority: Minor
-
Resolution: Obsolete
-
Affects Version/s: Current Version
-
Fix Version/s: Far Future
-
Component/s: OIOIOI
-
Labels:None
Description
[14/Mar/2017 14:32:48] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:32:58] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:09] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:19] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:29] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:40] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:50] "GET /c/aaaa/status/ HTTP/1.1" 200 433
Using a push protocol (an idle connection waiting for data from server) would be better, since an idle connection uses less power than an active one.
[14/Mar/2017 14:32:58] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:09] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:19] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:29] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:40] "GET /c/aaaa/status/ HTTP/1.1" 200 433
[14/Mar/2017 14:33:50] "GET /c/aaaa/status/ HTTP/1.1" 200 433
Using a push protocol (an idle connection waiting for data from server) would be better, since an idle connection uses less power than an active one.
Activity
- All
- Comments
- History
- Activity
- Transitions
- Commits
Feel free to reopen it or create a new one if it's still relevant.