|
From: Michael A. <mic...@ze...> - 2004-03-21 01:56:10
|
Hi, When a setString() is called on a SQLConfig object, it immediately passes the values to it's server (a SQLConfigService, funnily enough), which writes it to the database. In addition, the saveConfig method on the SQLConfigService class doesn't do anything. I was thinking, it makes more sense to me if the setString() call does *not* pass the call to the service object and save immediately to the database, but simply changes it's own cache value. Then, when some or other client code calls to saveConfig() on the SQLConfigService, that's when the service retrieves the cached updates and the data gets written back to the database. That way it can all be done in a single transaction, as well. Thoughts, please, anybody who cares, one way or the other... Cheers... MikeA |