You may assume that at any moment, at most one program is accessing the database file; therefore your locking system only needs to be concerned with multiple concurrent clients of your server.
kktec<br />SCJP, SCWCD, SCJD<br />"What we observe is not nature itself, but nature exposed to our method of questioning." - Werner Heisenberg
Originally posted by oli renard:
Hello,
This seems fair enough, except that I cannot help thinking of a situation where the db file being used in local mode by user 1 is the same file being used in server mode by user 2. For example, let's say that I run the application on machine A in local mode and I specify my db file's location as on machine A. Then another person runs the server on machine B and specifies the same file as mine (i.e. on machine A) as their db file. Surely, since both users are accessing the same file, local mode must be written in such a way as to ensure that the data is updated in a manner which is as consistent as the server mode.
Oli
Regards, George
SCJP, SCJD, SCWCD, SCBCD
Originally posted by oli renard:
They clarify the fact that I will assume that standalone mode means exclusive access to my local db file and that I do not need to specify the db file location when I start the server.
However, I am still very confused about the other 2 modes, i.e. server and network modes. How are these different? What do you actually mean by "server"? Is it a database server or the RMI server or something else?
Regards, George
SCJP, SCJD, SCWCD, SCBCD
The answer to the first senetence is that I can prompt the user to specify this when they start the server. As for the second, I am not sure. Can you please enlighten me on these 2 points please?Somehow the server needs to know where the db file is located. Somehow the network client needs to know where the database server is located.
Regards, George
SCJP, SCJD, SCWCD, SCBCD
Regards, George
SCJP, SCJD, SCWCD, SCBCD
Don't get me started about those stupid light bulbs. |