Got the results on 11/21/2001. (Nice Thanksgiving email!) Some details: General Considerations: 68/72 Documentation: 10/10 Object-Oriented Design: 6/6 GUI: 20/20 Data conversion program: 10/10 Server: 31/37 Did not extend Data, did not track clients by id, did not check for orphaned locks, used rmi, gui was minimalist text fields, buttons, message dialogs. (no menus or textboxes) Based on the scoring it appears that I may have a different version of the assignment. I am not sure what could be improved on General Considerations or Server. However, frankly I am ready to move on. I focused on the locking design, parts of the gui usability and oo design. (The oo design could have been better, though.)
Congrats, Glenn ! If you havent tracked client with id's, then otherwise how did u tracked clients for, which client, hold a lock on a record for modification ? I am curious !
posted 18 years ago
The code does not know which client held a lock. The lock knows which record was locked or if the entire database was locked. Was there a requirement to track client identity? --glenn [This message has been edited by Glenn Opdycke-Hansen (edited November 25, 2001).]
re: design patterns I did not use many design patterns. I did create a class for displaying names and values. This was used often for displaying the details of a flight, so a class helped manage the details. The factory pattern was helpful for creating data client objects remote/local. re: Directories I created the following packages for the client code. -client --model --view This helped organize the classes for MVC pattern. --glenn
Yup, yup, yup. Tiny ad:
Devious Experiments for a Truly Passive Greenhouse!