This is a common wish list question and shown in Figure 1.0 below. The problems however are not so simple.
The problems for concurrent access are
described in this wiki
Client systems A,B,C can easily step on the changes from one another.
Even *IF* the application attempts to control access with flock(), that is only good for controlling multiple uses of that same application on ONE host, not all hosts.
Figure 2.0 is the typical DMBS solution where one host has the DMBS server and all clients A,B,C access the server (S) directly and the server program is the sole access to the file(s).
Without a DMBS server, say shared files on NFS or a Windows Sever, we get back to Figure 1.0 and still need concurrency control.
CIFS is a design to handle that, but
the client program needs to be coded so as to implement the CIFS locking.
(unless specifically stated,
do not assume any program has network sharing implemented!)