One thing that comes to mind for me is bit in the instructions that state at most only one program is accessing the database.
I used that assumption to my advantage when I, I'd like to think, ensured my application is threadsafe. What I didn't do is ensure that it's not possible for multiple clients to access the database, by clients I mean database clients not gui clients.
So you're running a server, and start a client in local mode accessing the same database, what behaviour can you expect? Do you allow a 2nd client to connect?
According to my instructions I shouldn't have to worry about that, but perhaps it's expected that we cater for it in some way or another such as opening the file exclusively and throwing the exception when it's open.
Has anyone actually scored 100% without catering for this scenario? Because that would rule out this possibility.
[ August 17, 2005: Message edited by: Ta Ri Ki Sun ]
I used that assumption to my advantage when I, I'd like to think, ensured my application is threadsafe. What I didn't do is ensure that it's not possible for multiple clients to access the database, by clients I mean database clients not gui clients.
So you're running a server, and start a client in local mode accessing the same database, what behaviour can you expect? Do you allow a 2nd client to connect?
According to my instructions I shouldn't have to worry about that, but perhaps it's expected that we cater for it in some way or another such as opening the file exclusively and throwing the exception when it's open.
Has anyone actually scored 100% without catering for this scenario? Because that would rule out this possibility.
[ August 17, 2005: Message edited by: Ta Ri Ki Sun ]