Hi, am I right that such a solution requires a locking system for the
files? (otherwise conflicts/overwrites will happen soon).
Since we are in an intranet, both clients (users) and the server can access
the same files repository, so maybe there is no need for a complicated
client/server soluti
Note that 'web2py as client' could be running as daemon (service) along
windows booting, so users will not feel the difference.
On Wednesday, December 19, 2018 at 10:10:30 PM UTC+3, Val K wrote:
>
> I thought about the same problem and only see the following dropbox-like
> almost universal sol
I thought about the same problem and only see the following dropbox-like
almost universal solution:
web2py as server + web2py as client (under latter I mean .exe-distributive
on the shared drive, so it will running on client machine and has access to
filesystem, to connect with central server
Hi,
- any type of files, but most common are the usual office ones: .doc,
.docx, pdf, xls, xlsx.
- currently people are using simply a shared drive, with an unmanageable
number of files and subfolders, they want to shift to a structured
approach, were files are linked to a datab
4 matches
Mail list logo
