on 5/12/2000 7:18 AM, Ganesan Sankara <[EMAIL PROTECTED]> wrote:
> One of the basic flaws I noticed it does not support database commitment
> control. Each operation like insert,update,delete seems to getting new
> connection from pool and once done return back the control. A typical
> transaction block will include lot of tables and will be committed at the
> end once all operations are successful. This support seems to be missing in
> Peer class?
Yes. Direct support of Transactions is still missing in a "cool" way.
Although, you can create a transaction in your own Peer classes by simply
grabbing a connection, holding onto it, doing your transaction stuff and
then letting it go after everything completes.
It isn't a design flaw, it is an implementation detail. If you would like to
contribute and make something that is "cool", then feel free.
-jon
--
Java Servlet Based - Open Source | Collab.Net
Bug/Issue Tracking System | now hiring smart people
<http://scarab.tigris.org/> | <http://Collab.Net/jobs/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
