You're thinking wrong if you're implementing the entire database logic twice.
You only need it once, nicely decoupled from the user interface, and have either one of 2 access layers (networked or local) in between the user interface and database which route the traffic.
Kevin Mc Cusker
Joined: Aug 06, 2003
Im not intending on implementing it twice, I just cant see how I can delete a record in local mode without having to also perform a lock, as the delete record method requires a lockCookie as a parameter.
My Data instance is mainly composited of lockManager instance and a DAO that performs CRUD operations. It's simple. If the specified lockManager instance is null, locking is bypassed. And obviously locking is not needed in local mode since
your locking system only needs to be concerned with multiple concurrent clients of your server
[ September 09, 2006: Message edited by: Oricio Ocle ]
we do require locking in local mode i guess.. theres only a single client in this mode but for testing they can generate multiple threads and try to access the database or may be the database will be accessed by other applications running on the machine (which may work as client).. so i guess locking should be provided in Local mode also ..Can anyone verify this ...
SCJP 1.4<br />SCWCD 1.4(91%)<br />Working on SCJD -Bodgitt & Scrapper Constructions...<br /> <br />"It takes 43 muscles to frown & 17 to smile but it doen't take any to just sit there with a dumb look on your face .. Keep Smiling "