On 5/16/2024 2:17 PM, David G. Pickett via gnucash-user wrote:
Yes, if gnucash was running as a remote service, it might be able to deal with
multiple users. Imagine that gnucash becomes a web service and the user
interface is a relatively simple web page. Even in this scenario, you would
need to avoid processing too much in JavaScript and local files under the web
browser, so the remote server has updated data at all times.
But already gnucash often leaves a modified transaction not committed to the
saved storage, even with auto save. When my cron job kills gnucash to update
prices, it sometimes loses such transactions typed but not committed by leaving
that line. It might be an improvement to remedy that!
Gnucash can work with multiple SEQUENTIAL users (one at a time)
Gnucash cannot work with multiple CONCURRENT users (more than one at a
time). That requires running under the control of a DBM.
This issue is really beyond almost all end users. The issues involved
with concurrent processing, and the various solutions that can be
employed, would usually be learned at the upper levels of Computer
Science program. Look for a course with a name like "concurrent
processing".
Michael D Novack
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
