Hi, If we run the FBN assignment mode in the standalone mode then we are not using RMI or sockets. If a user happens to start two clients from the same machine in the standalone mode. In effect we are having two JVM's running. db.db file is part of client.jar How do we make sure that we dont end up screwing the data file because our locking etc will be handled in the JVM. In case of remote clients we can handle this because all our i/o access to the file is via one single class on the RMI server. But in the standalone case havingmultiple clients. we will definitely end up screwing the data file.. Any advises/suggestions/clues.
Akshay Kumar Sharma<br />**********************<br />Good Better Best <br />Never Let it rest<br />For your good is better<br />and the better is the best
Hi Akshay I dont think we have to worry about someone starting two separate applications using the same DB. In the new assignment it is specifically stated that we dont have to worry about this. Regards. Andrew
Hi Akshay Sorry I wasnt clear. I did see that you had mentioned that you were doing FBNS. I also did this. I did not try to handle the case where two applications could both write to the file at the same time. My comment about the new assignment was just for information - if they have explicitly stated it is not required in the new assignment, then I think it is reasonable to assume the same for the old assignment. Regards, Andrew