Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
Sessions |
Fri, May 4 2007 11:18 PM | Permanent Link |
"Lance R" | Tim,
Something I noticed in 1.02 is that with the Manager app running in Client / Server mode, things seem to work pretty well unluss you stop and restart the server. The Manager will complain that the "connection has been interrupted or timed out and needs to be re-connected... Would you like to continue with the connection". If I say Yes... I'll get a 1107 error with the Sesion ID #xxxxxxx is no longer present. Understandable. However you need to then disconnect the session, reconnect the session to get back where you were. Shouldn't there be a more "graceful" way to say "Connection was lost, would you like to reconnect? ". Then if not, you should close off everything in the display and take you back to the first step of connecting a session. If so, it should reconnect with a new / same session and start where you last were. I'd like to know of a good "clean" way to deal with sessions as I use the compent exclusively in C/S mode and will run into situations where they will walk away from my app for a long period and want to start where they left off. Lance |
Mon, May 7 2007 12:02 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Lance,
<< Shouldn't there be a more "graceful" way to say "Connection was lost, would you like to reconnect? ". Then if not, you should close off everything in the display and take you back to the first step of connecting a session. If so, it should reconnect with a new / same session and start where you last were. >> I'll see what I can do in the EDB Manager. It really depends upon whether I can trap the exception properly for dealing with a reconnection that fails due to the session being removed by the ElevateDB Server. << I'd like to know of a good "clean" way to deal with sessions as I use the compent exclusively in C/S mode and will run into situations where they will walk away from my app for a long period and want to start where they left off. >> The only way to ensure that this doesn't cause issues like the above, is to configure the dead session expiration time on the ElevateDB Server for a very large amount of time, just like with DBISAM. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, May 8 2007 12:55 AM | Permanent Link |
Lance Rasmussen Jazzie Software Team Elevate | Thanks Tim,
I was also debating about putting a timer to do a ping or get server time in order to help try keep the connection alive. Lance "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:94D0EDEC-0138-4E2F-AC68-03605BA356DD@news.elevatesoft.com... > Lance, > > << Shouldn't there be a more "graceful" way to say "Connection was lost, > would you like to reconnect? ". Then if not, you should close off > everything in the display and take you back to the first step of > connecting a session. If so, it should reconnect with a new / same > session and start where you last were. >> > > I'll see what I can do in the EDB Manager. It really depends upon whether > I can trap the exception properly for dealing with a reconnection that > fails due to the session being removed by the ElevateDB Server. > > << I'd like to know of a good "clean" way to deal with sessions as I use > the compent exclusively in C/S mode and will run into situations where > they will walk away from my app for a long period and want to start where > they left off. >> > > The only way to ensure that this doesn't cause issues like the above, is > to configure the dead session expiration time on the ElevateDB Server for > a very large amount of time, just like with DBISAM. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > |
Tue, May 8 2007 7:41 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Lance,
<< I was also debating about putting a timer to do a ping or get server time in order to help try keep the connection alive. >> Just use the RemotePing:=True setting for the TEDBSession in that case. I thought you were wanting a situation where a removed session could be reconnected. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, May 11 2007 3:39 AM | Permanent Link |
Lance Rasmussen Jazzie Software Team Elevate | Well.. Actually. That is what I want. But remotePing will help keep it
alive at least. Lance "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:0E61EE1F-BFEC-418C-B5F0-3C857764C0EC@news.elevatesoft.com... > Lance, > > << I was also debating about putting a timer to do a ping or get server > time in order to help try keep the connection alive. >> > > Just use the RemotePing:=True setting for the TEDBSession in that case. I > thought you were wanting a situation where a removed session could be > reconnected. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > |
This web page was last updated on Monday, May 6, 2024 at 03:23 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |