That, perhaps, could be a problem, but I see it more of a code design
problem. In the case of C/S programming, one should *never* leave a
transaction open, waiting for user input. We never do that. It's asking for
transaction gap problems.

Best regards,
Fred Wilson
SE, Bell & Howell
fred.wilson@... <mailto:fred.wilson@...>


-----Original Message-----
From: Paul Schmidt [mailto:paul@...]
Sent: Tuesday, December 04, 2001 10:19 AM
To: ib-support@yahoogroups.com
Subject: [ib-support] Hibernation



As various species of animal settle down for a long winters nap,
naturally we think about computers, modern machines with power
management, that can also hibernate.

What happens if you open a transaction, then pack up for the day,
the machine is still running, it's set up so that in an hour it
hibernates. The transaction is still open.

Is there a way for gds32.dll to detect that the machine is about to
hibernate, so that the transaction can be terminated, either
committed or rolled back, so that it isn't held open for a long period
of time, suppose the user is off on vacation for 4 weeks, an OAT
that is 4 weeks old would not be a good idea.

Paul



Paul Schmidt
Tricat Technologies
paul@...
www.tricattechnologies.com


Yahoo! Groups Sponsor

ADVERTISEMENT

<http://rd.yahoo.com/M=178320.1681224.3270152.1261774/D=egroupweb/S=17050077
09:HM/A=879173/R=0/*http://www.fastweb.com/ib/yahoo-76f>

<http://us.adserver.yahoo.com/l?M=178320.1681224.3270152.1261774/D=egroupmai
l/S=1705007709:HM/A=879173/rand=481920915>

To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .