Prev: The NNTP exodus continues.
Next: VB6 to Web
From: Dee Earley on 13 May 2010 08:40 On 10/05/2010 23:17, David wrote: > I have a program (I'm the client) that connects to a server. > The server reboots everyday (out of my control) at 4:45:00 for three > seconds. > > At this time my program hangs (stops receiving data) and does Not > continue after the three second interruption. > > Is there a solution to reestablish or maintain this connection other than: > > 1) manually reconnecting, or > 2) setting up a time tracking program to have XP close and then > re-start my program -- (can see problems with this if the > server changes reboot time) What do you do in your software to "connect"? Can't you just do that if you receive no data for "a while" (tm). If there is no explicit connection sequence then you will just need to recreate the objects as Nobody said (still an annoying name :). If they are full activex controls with no connection methods, you will need to unload and recreate the form (maybe move them onto a sacrificial form?) -- Dee Earley (dee.earley(a)icode.co.uk) i-Catcher Development Team iCode Systems (Replies direct to my email address will be ignored. Please reply to the group.)
From: David on 13 May 2010 11:10 Was trying to stay away from a "timer" solution -- if at all possible. One possibility may be to have a timer which monitors the timestamp being received and if it the time doesn't change for a minute then relink to the server. Kind of system intensive but should work. Thanks to all for input. Will consider this thread closed. "Dee Earley" <dee.earley(a)icode.co.uk> wrote in message news:%23l10plp8KHA.4604(a)TK2MSFTNGP04.phx.gbl... > On 10/05/2010 23:17, David wrote: >> I have a program (I'm the client) that connects to a server. >> The server reboots everyday (out of my control) at 4:45:00 for three >> seconds. >> >> At this time my program hangs (stops receiving data) and does Not >> continue after the three second interruption. >> >> Is there a solution to reestablish or maintain this connection other >> than: >> >> 1) manually reconnecting, or >> 2) setting up a time tracking program to have XP close and then >> re-start my program -- (can see problems with this if the >> server changes reboot time) > > What do you do in your software to "connect"? > Can't you just do that if you receive no data for "a while" (tm). > > If there is no explicit connection sequence then you will just need to > recreate the objects as Nobody said (still an annoying name :). > If they are full activex controls with no connection methods, you will > need to unload and recreate the form (maybe move them onto a sacrificial > form?) > > -- > Dee Earley (dee.earley(a)icode.co.uk) > i-Catcher Development Team > > iCode Systems > > (Replies direct to my email address will be ignored. > Please reply to the group.)
From: Dee Earley on 13 May 2010 12:26 On 13/05/2010 16:10, David wrote: > Was trying to stay away from a "timer" solution -- if at all possible. > > One possibility may be to have a timer which monitors the timestamp > being received and if it the time doesn't change for a minute then > relink to the server. Kind of system intensive but should work. Even checking a timestamp once a second is far from system intensive : ) A minute wouldn't even be noticable. Note that it doens't need to run all the time, just disable it and enable it when you receive data with an interval of 5s. This won't ever run until it needs to do anything, 5s after the last data received. -- Dee Earley (dee.earley(a)icode.co.uk) i-Catcher Development Team iCode Systems (Replies direct to my email address will be ignored. Please reply to the group.)
From: David on 17 May 2010 21:48
Thanks for input. Please consider this thread closed. David "Dee Earley" <dee.earley(a)icode.co.uk> wrote in message news:eDL5Ikr8KHA.5848(a)TK2MSFTNGP06.phx.gbl... > On 13/05/2010 16:10, David wrote: >> Was trying to stay away from a "timer" solution -- if at all possible. >> >> One possibility may be to have a timer which monitors the timestamp >> being received and if it the time doesn't change for a minute then >> relink to the server. Kind of system intensive but should work. > > Even checking a timestamp once a second is far from system intensive : > ) > A minute wouldn't even be noticable. > > Note that it doens't need to run all the time, just disable it and enable > it when you receive data with an interval of 5s. > This won't ever run until it needs to do anything, 5s after the last data > received. > > -- > Dee Earley (dee.earley(a)icode.co.uk) > i-Catcher Development Team > > iCode Systems > > (Replies direct to my email address will be ignored. > Please reply to the group.) |