ok, I´m back ... so what were my decisions ?
First of all ... I had the URLyBird ...
3 Tier Thin-Client Architecture :
Server Layer (accessing the data file)
Business Layer (on Server)
Client Layer
No Logging (just printStackTrace at the three layers)
No 48 hours rule implemented
RMI as network approach
No Unbook - Button
Filtering of all Non-Exact matches in the business layer
Thread safety was done using java.concurrent.locking
I used the following
pattern:
DAO (for accessing the data file)
Business Delegate (for encapsulating the network approach)
Factory (for getting the dao)
Wrapper (for the JTableModel)
MVC