Originally posted by dave wav:
within the class DataServer, I implements a method called bookFlight.
Thereby mixing general-purpose and application-specific code, mixing two completely different levels of abstraction, and inhibiting the reuse of a potentially completely reusable server.
Not a good idea. Consider moving bookFlight() to the front end. Remember this architecture:
UI <=> Business Logic <=> Persistence
Whether the UI is Swing, JSPs, or something else; whether the business logic is a conceptual layer in the front end (as, IMHO, in FBN) or an
EJB container; whether the persistence is an enterprise-level SQL database or a flat file; whether it all runs inside one JVM or each layer is represented by a farm of heavyweight multi-CPU servers -- you will find these layers, at a minimum, in every well-designed non-trivial software system. Well, almost every
Mix the layers, and the abstraction represented by each layer, at your own peril.
- Peter