I used the thin client approach and used the ThreadID as identifier for the locking mechanism.
As there was no Cookie in my interface this architecture really made sense.
This made my locking solution very easy and small, I implemented it in the Data Class itself.
For the GUI I used MVC, letting the controller act as a event listener/handler, where all the view components use the controller as the event handler.
This way I have a clean View class (no inner classes) and a nice separation of view and actions.
Nam Ha Minh wrote:Great!
And how long did you prepare for that?
I did not know what to expect from the assignment, so my preparation was minimal.
My greatest resource concerning important decisions were all the discussions here at Javaranch!!
I have spend lot of hours here reading about fat/thin client and so on.
I have a full time job so I had to do everything in my spare time
Still I found the 6 months enough time to complete the project.