[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] client tcp/ip and Postgres timeouts

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] client tcp/ip and Postgres timeouts
Date: Sat, 16 Aug 2008 20:42:47 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Sat, Aug 16, 2008 at 09:52:15AM -0700, James Busser wrote:

>> He suggests running an empty query every so often.
>> If dropped connections appear to become a problem I'll add
>> that to GNUmed.
> I was just aiming to prevent data loss as a consequence of unsaved data 
> sitting in an idle GNUmed client session

I know.

> In parallel to running an empty query every so often (if needed), may we 
> desire an otherwise idle GNUmed session would
> - at minimum, after some suitable period of inactivity (maybe q15-30  
> minutes), attract the attention of the user?

The problem here is to know the "suitable period". It may be
well hidden in several layers of gateways and routers.

Therefore I'd rather suggest running an empty query at a
configurable interval.

> - possibly, if the user does not acknowledge:
>       auto-save progress notes?

Hm, hm. Not sure about that.

>       enter some form of "locked" mode
>       -> would require the user re-provide their password
>       (not that any "locked" mode is yet supported...)

The relevant timer is already there ... :-)   We just need
"something" to get done when it fires.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]