>diff -git a/netwerk/protocol/http/nsHttpConnectionMgr.cpp b/netwerk/protocol/http/nsHttpConnectionMgr.cpp >+void Which means you can just return timeToLive directly. No need, since you control all the callers. >diff -git a/netwerk/protocol/http/nsHttpConnection.cpp b/netwerk/protocol/http/nsHttpConnection.cpp >+nsresult nsHttpConnection::TimeToLive(PRUint32 *timeToLive)
React idle timer timeout for mozilla firefox Patch#
Xulrunner patch to remove polling from pruning of connections Of course it is better to fix the real problem instead of making these kind of fixes, so better solution needs to be done, but this kind of solution can be used for idle state if we don't get better solution for it soon.Ĭomment on attachment 473031 > any potential problems with the display going off, but lots of network activity > before the display goes off (if no networking is going on).
> That would make this work in a better way, since it could halt the timer even By the way how is the progress for system state notifications? Yes, using display-off and platform specific checks here is a bit confusing, but since this is not optimal solution it was narrowed for Maemo 6 and at the moment display-off notification is only thing that is close to idle state for which this patch aims for. > activity resumes, the timer could be resumed. > again if the network has been idle for more than 15 seconds. When the timer fires, it could then stop itself from firing > might know when the last network activity (in the sense needed for pruning idle From my perspective, I think that we shouldn't have platform-specific checks in
0 kommentar(er)
