Define Maintaining Data on a Per Client Basis
Perhaps the most dramatic syntactical programming change for the application developer of client – server applications is maintaining data on a per – client basis. It is most beneficial to architect applications initially with per- client data in mind. Because servers ( or serving application components) traditionally perform work on behalf of many client, data accessed by server logic components must be unique for each client. Traditional variable allocation and use under C poses interesting problems for the application developer. Data is usually maintained as global or local.
When manipulating data on behalf of many clients, global data can not be guaranteed to be unique. It is therefore necessary to recode applications for per-client data use. Inc, the mechanism for redevelopment is to group all data pertaining to each requester of services(client) as a structure. Generally an instance of the structure will be created for each requesting client. The data modifications made by the server application component are therefore based on the individual client’s user data structure. C++ enforces modular data access by grouping all data and functions within a class. This encapsulation provides the C++ developer with a more normal mechanism for per – client data access.