James,
You don't need to go all the length to creating a sqlite proxy RPC as has
been suggested.
Your service could implement one thing only - a lock to the database file
(external to the SQLite locking mechanism, of course). So it only needs to
serialize concurrency; the client does the RPC (via
] On
Behalf Of R Smith
Sent: 11 January 2018 10:45
To: sqlite-users@mailinglists.sqlite.org
Subject: Re: [sqlite] SQLite Application Server Concurrency
On 2018/01/11 11:06 AM, James Colehan wrote:
> Hi,
>
> I am looking for some advice on using SQLite for my given situation.
>
> My
: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of James Colehan
Sent: Thursday, January 11, 2018 3:21 AM
To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org>
Subject: Re: [sqlite] SQLite Application Server Concurrency
Hi Simon,
Thanks for getting b
I have several such applications, running in industrial environment.
I always use a TCP server on 'X' and TCP client on 'Y' with some simple,
specialized http-like protocol on top.
All this can be implemented very easy, especially if you don't need a top
performance and millions of clients.
On 2018/01/11 11:06 AM, James Colehan wrote:
Hi,
I am looking for some advice on using SQLite for my given situation.
My system involves a windows network. On PC 'X', I have an SQLite database with
a process that handles amendment's to the database ie INSERTS, DELETES and
UPDATES. Also, on
...@mailinglists.sqlite.org] On
Behalf Of Simon Slavin
Sent: 11 January 2018 09:13
To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org>
Subject: Re: [sqlite] SQLite Application Server Concurrency
On 11 Jan 2018, at 9:06am, James Colehan <jcole...@gtt-training.com> wrote:
On 11 Jan 2018, at 9:06am, James Colehan wrote:
> My concern is that I have a requirement to query the database on PC 'X' from
> other PC's. Basically, performing (SELECT) statements from stations 'Y' and
> 'Z'. This creates a client/server situation that I
7 matches
Mail list logo