This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Welcome to the world of Swing...
Do I need to worry about this kind of thing in the GUI, or am I thinking too hard.
You probably do not want users booking the same seat twice , but how you handle it is up to you.
If you create a separate thread to do the booking, you will have a more responsive networked client, but you will have to do something to ensure that only one transaction is outstanding at any given time.
If you do not create a separate thread to do the booking then there is no way that the user will be able to book twice. But then there is the risk that the system may appear unresponsive if there are network problems.