It's been rumoured that [EMAIL PROTECTED] said:
>
> It should be clear why Transaction engine and DB engine should stay close;
> they will need to communicate quite a lot of data in order to negotiate
> the parts that are to be submitted to the GUI. A "for instance" would
> be that if the DB does not support computing sums/balances internally,
> the transaction engine will need to do so, and will have to talk heavily
> with DB.
I had always hoped/envisioned that the engine could run both in the server
*and* the client. In the client, it provides a convenient programming
API, and a data cache. In the server, it provides transactional
capabilities & functions (and a convenient programng API).
--linas
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
