On Thu, Jun 14, 2012 at 10:35 AM, Paul McNett <[email protected]> wrote: > 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.
Since the implementation is in dBackend, I wouldn't put it in the UI because you are mixing layers then. I would leave it because it's running fine as it is right now with a minimal amount of overhead. Also, because it's on dBackend, we never actually run the thread with a dConnection object (just the backend specific connection object) and so the cursor is actually just a straight backend cursor class without the dabo mixins. My main reason for trying it in the first place (once I discovered it was there) was if I leave a program open and then leave it in the background or lock the computer to step out of the office, I come back and try to do something and then get a "MySQL server has gone away" error. I am hoping I can fix that with the KeepAliveInterval, but it still won't do any good if you sleep a laptop. Could we catch connection errors like that and attempt an automatic reconnect? Regards, Nate _______________________________________________ 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/CAGcHxzbh=sJe_VqeitdUTGcu0Bj7055m15SCK0AED29v9aJx=a...@mail.gmail.com
