Re: DBTransactions and DBConnections

This is a multi-part message in MIME format...

------------=_1112283979-15232-176
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Hi Sinisa,
    Thanks for the info.  So, from the sounds of it, the scenario I 
described (of the auto-write setting possibly getting extended to something 
other than a simple true/false setting that might periodically perform the 
.write() call) is unlikely.  It also sounds like the "standard" DODS 
configuration was/is considered to include autowrite be always on - in that 
case, it might be worth making the default value of the DODS configuration 
setting for AutoWrite be true rather than false.

    By the way, is there any particular reason that the 
StandardDBTransaction continues to accept Transaction objects, but ignores 
all Transactions passed to it other than subclasses of CoreDO?  I found this 
particular aspect of the API to be a little misleading.

Mike.

----- Original Message ----- 
From: "Sinisa Milosevic" <[email protected]>
To: <[email protected]>
Sent: Wednesday, March 30, 2005 12:11 PM
Subject: Re: [dods] DBTransactions and DBConnections


Hi,

Thanks a lot for your comments. We had a lot of discussion in our team when
we implemented autowrite and autosave options.

First you are right that you can get 'wrong' result if you doesn't use
autowrite option and has some modifications in transaction - specially
creating new DOs, without calling write method. We decided to implement
following scenario:
if you use autosave and autowrite and transaction cache in your application,
DODS should guarantee to you that you always get right results. That's a way
how application should use DODS transactions (nice DO aggregation).

If for some reasons, you can't use autowrite and autosave options,
application (developer) must provide that write() method will be called
after some modifications in transaction which can cause wrong query results
in the same transaction.

We can discuss a lot about this 'feature' is it a right way or not. We just
want to have clean situation. If autowrite is false, we don't want that DODS
automatically calls write method without application control.

By the way, DODS has a modular structure and you can change your templates
and use 'custom' templates or you can easily write new Transaction
implementation and use it in your application (setting in conf file which
implementation will be used)

Thanks again for your suggestions. These are always very useful for us.

Regards,
Sinisa




------------=_1112283979-15232-176
Content-Type: text/plain; name="message.footer"
Content-Disposition: inline; filename="message.footer"
Content-Transfer-Encoding: 8bit


--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

------------=_1112283979-15232-176--