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
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
