My VFP app connects to a MYSQL (soon to be a MariaDB) server running on
a dedicated Linux box via the Internet. My current design is that when
the app starts up it connects to the MySQL server and then keeps that
connection 'live' by using a timer every 15 minutes, sending 'SELECT
@@identity' in case there is no user activity.
I'm running into frequent situations where the workstation's Internet
connection seems to be getting dropped briefly (by the ISP) and the next
attempt to access the server by the app on that workstation will trigger
"there is no connection" errors. (loosely paraphrased) The app then
reconnects and moves along.
Would it be smarter to
- connect when needed
- send/get data needed
- disconnect
each time I need to access the server? I had avoided this assuming it
would slow things down during the connection process, but, maybe this
would be preferable?
I know that testing is the best way to figure this out, but I'm sure
this is old stuff to many of you and you've already been there done that.
Thanks for any wisdom or opinions.
Mike Copeland
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
