On 6/14/12 5:29 AM, Nate Lowrie wrote: > Log: > Rewrote the KeepAliveInterval to enhance performance. I kept the same thread > structure but moved all of the object declarations to the front so they > weren't > created with every iteration of the loop. I also increased the sleep time to > 5 seconds, which is long enough to not cause a problem, but short enough where > the application will end soon after the main is finished. Lastly, I added a > lastExecuteTime to the dBackend object, which gets updated on a cursor execute > statement. The KeepAliveInterval is timed from the last cursor execute > statement > instead of a constantly running clock, further minimizing impact to the UI. > Now, even with a 10 second KeepAliveInterval, the performance impact to the > app > is negligible.
Sounds good. Any ideas for removing the thread? If this were in the UI layer, we could just use serial callAfterInterval(interval, keepAlive) calls. I guess we really can't do that because there is no non-UI event loop running. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
