babeldoc-devel

[Babeldoc-devel] Possible changes to SQL Config immediate write

[Michael A. <mic...@ze...>]

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

Re: [Babeldoc-devel] Possible changes to SQL Config immediate write

[Dejan K. <dej...@ya...>]

Hi Mike, 
First of all, I must say that I have never used that
code so I am probably not aware of all issues
regarding to SQlConfig. I know that Erik has some
problems with initial SqlConfig implementation since
his system was required to run in clustered enviroment
where all nodes should be aware of changes made in one
node (without restarting). So, (if I remember well) he
dropped all cache usage in SqlConfig and every change
made in configuration is immediatelly written to
database. 

Now, I am not sure if this could be done better.
Perhaps, you could introduce some new config option
that would enable cache usage in SqlConfig.

I am not sure if this is all true, but you could
search mailing list. Also, I guess that old
SqlConfig(Service) implementation is still in CVS so
you can look at the CVS history for these files. 

regards,
Dejan

--- Michael Ansley <mic...@ze...> wrote:
> 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
> 
> 
> 

> ATTACHMENT part 2 application/pgp-signature
name=signature.asc



__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html

Re: [Babeldoc-devel] Possible changes to SQL Config immediate write

[Michael A. <mic...@ze...>]

Hi,

Excellent, this is exactly the kind of information I was looking for.  I
never thought about the case of clustered servers.  I'll work out how to
build that into the design, and see what I come up with.

Cheers...


MikeA


On Sun, 2004-03-21 at 11:16, Dejan Krsmanovic wrote:
> Hi Mike,=20
> First of all, I must say that I have never used that
> code so I am probably not aware of all issues
> regarding to SQlConfig. I know that Erik has some
> problems with initial SqlConfig implementation since
> his system was required to run in clustered enviroment
> where all nodes should be aware of changes made in one
> node (without restarting). So, (if I remember well) he
> dropped all cache usage in SqlConfig and every change
> made in configuration is immediatelly written to
> database.=20
>=20
> Now, I am not sure if this could be done better.
> Perhaps, you could introduce some new config option
> that would enable cache usage in SqlConfig.
>=20
> I am not sure if this is all true, but you could
> search mailing list. Also, I guess that old
> SqlConfig(Service) implementation is still in CVS so
> you can look at the CVS history for these files.=20
>=20
> regards,
> Dejan
>=20
> --- Michael Ansley <mic...@ze...> wrote:
> > Hi,
> >=20
> > 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.
> >=20
> > 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.=20
> > 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.
> >=20
> > Thoughts, please, anybody who cares, one way or the
> > other...
> >=20
> > Cheers...
> >=20
> >=20
> > MikeA
> >=20
> >=20
> >=20
>=20
> > ATTACHMENT part 2 application/pgp-signature
> name=3Dsignature.asc
>=20
>=20
>=20
> __________________________________
> Do you Yahoo!?
> Yahoo! Finance Tax Center - File online. File on time.
> http://taxes.yahoo.com/filing.html
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel