I'm getting ready to submit any time now.
My Controller is in the GUI package and has a boolean parameter for local or not. It populates the table and the combo boxes I use for Search and basically does 'find' and 'reserve'.
I do not expose lock/unlock to the client. I think I have a 3 tier thick client. One of those replies implied that not exposing lock/unlock to the client is thin client. I still think I am thick and 3 tier, but am a little
Anne Crace wrote:My thinking is the Controller IS business layer
Mark O' Sullivan wrote:Ya, this business approach looks great, I'm just thinking of where I actually could do the locking with this approach as within my assignment, I have a unique cookie returned to client for some methods, e.g. lock. Would this be done then in the business logic section?
I'm at the point that many others have reached and just want to get rid of the $%$@ thing!
Please don't ask me to read that thread "Should lock methods be callable from the client". I have it bookmarked and have read it many times! lol!
I think I'm good here I have a hard copy of the specs with all the 'musts' highlighted and checked them off if they were OK.
Just make sure you don't miss any "must", and it should be fine!