Question

Consider a simple server that carries out clients requests without accessing other servers. explain why it is generally not possible to set a limit on the time taken by such a server to respond to a client request. what would need be done to make the server able to execute requests with in a bounded time. is this a practical option?

Answer 1

Consider a simple server that carries out clients requests without accessing other servers. explain why it is generally not possible to set a limit on the time taken by such a server to respond to a client request. what would need be done to make the server able to execute requests with in a bounded time. is this a practical option after that then have to take help from a service and involved wireless speed internet

Answer 2

Answer:

The rate of arrival of client requests is unpredictable.

If the server uses threads to execute the requests concurrently, it may not be able to allocate sufficient time to a particular request within any given time limit.

If the server queues the request and carries them out one at a time, they may wait in the queue for an unlimited amount of time.

To execute requests within bounded time, limit the number of clients to suit its capacity. To deal with more clients, use a server with more processors. After that, (or instead) replicate the service.

The solution may be costly and in some cases keeping the replicas consistent may take up useful processing cycles, reducing those available for executing requests.