i think i know the answer to this one, but then again, im not sure, so i wanted to check with everyone just in case...
where should the processing/controller logic for say booking a seat take place?
put all the "logic" in the code on the client side, where the client locks records, modifies records, unlocks records, etc
make a method bookSeat() that gets processed on the server side. all the client knows is whether the booking was successful or not.
ideally i think option B is better in terms of separation of work. the client shouldnt know about the database and how it works. it should just know it wants to do and requests that the work gets done.
however, on the other side of the card, why would the requirements require that the client implement the same public methods as the Data class? why force the providing of methods like lock() and add(), etc to the client if its not necessary?
am i just second guessing myself? (i tend to do that! heheh)
thanks for your help
[ January 29, 2002: Message edited by: Bruce Ichiban ]