We are developing a measurement tool in which is based on the client server architecture.
But the role of client is only getting connected to the server.
Once the client send a requests, the server manages :
1. Accepting the request
2. Storing all client information
3. Configuring the client
4. Running some tests on client
5. Getting results from client
6. Closing the client
So there is only once server instance and many client instances at the server side.
Also we are thinking of separating test, communication, measuring device classes separate.
Please can anyone help us designing the system at the server side.
What are the patterns that we can use...?