For development, until I get the machine going, could be as far as a local VM, or, a VM I build on one of our ESX boxes in the office. The connection would probably be via SMB while developing.
I'll start with the 10 seconds timeout on the remote. I've stumbled across a couple of examples Mr. Google has provided for me, but I didn't find much in the lines of remote access settings for lightweight use. On Thu, Mar 23, 2017 at 2:14 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 23 Mar 2017, at 5:45pm, Stephen Chrzanowski <pontia...@gmail.com> > wrote: > > > The remote > > system is a Linux based OS. […] > > How 'remote' is this ? What protocol is used to do the remote access ? > > > What would be a recommended way to setup the > > connections for a DEV-only arena where the below paragraph describes? > > … or is that what you’re asking for advice on here ? > > > By EXTREMELY LIGHT WEIGHT use, I mean I *DO* guarantee that although I > have > > one permanent open file handle to the database via SEP, and that Linux OS > > will only open a handle periodically while I'm writing the script, > > multiple accesses of reading or writing to the DB at the exact same time > > just will not happen. > > Set a timeout of at least 10 seconds on all connections to the database. > Apart from that I can’t think of anything you haven’t mentioned. I do more > complicated things by using SQLite as a back end to a web-facing system > without problems. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
