Yep - tried on LiveCode - no joy there so far. Cheers,
Terry... On 30/09/2010, at 3:54 AM, "Devin Asay" <devin_a...@byu.edu> wrote: > > On Sep 28, 2010, at 7:20 PM, Terry Judd wrote: > >> The problem of lengthy timeouts when trying to connect to a MSQL server that >> is down/offline is bugging me again. It seems like the default timeout is 60 >> seconds which is way too long to wait for a response but there's no obvious >> way to override it. The socketTimeoutInterval has no effect and while I've >> got some old code laying around that suggests setting an environment >> variable ($MYSQL_CLIENT_TIMEOUT) it doesn't work either. >> >> Any ideas? > > Terry, > > Have you tried this on LiveCard 4.5? According to the release notes, there > was an engine change that made opening sockets non-blocking, but I don't know > whether that affects MySQL connections. > > Devin > > Devin Asay > Humanities Technology and Research Support Center > Brigham Young University > > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution