Traditional Client Server Architecture

Hi

My instructions state:

The main architecture of the application must be a traditional client-server system. There are three key parts: the server-side data management system, the client-side GUI, and the network connection between the two.

My understanding of traditional client-server system is the client consists of the business logic and presentation and the server simply access the db. Is this correct?.

I have read the long topic on client v server locking. I have implemented my locking on the server by wrapping my business methods. Now I am thinking that this should be on the client due to the client server architecture. I guess I am just worried that I will fail if I leave things as is and submit.

Any thoughts ?

You're not in any danger of failing. Just read the best you can into it, and justify your choices. This statement is one of the more ambiguous -- don't sweat it.

Hi M,

As Nathaniel says, there is a lot of ambiguity in the instructions. In many cases this is deliberate - Sun wan't to see how you handle the ambiguity. The important thing to realise is that this is one of many parts of the assignment where you have to make a design choice. Which means that your choice should be mentioned in your choices document.

As mentioned in the thread "Should lock methods be callable by the client", where you implement your locking does not appear to affect your overall score.

Regards, Andrew

Thanks guys

You're welcome.