If I asked you to design a client server application that would work as a progressive slot machine (if you don't know what that is look it up before proceeding) client server application...what three choices would you make for that, why? Is the design much different from the time synchronization server?

Explanation:

Iterative vs Concurrent:

An iterative server handles both the association demand and the exchange engaged with the call itself. Iterative servers are genuinely straightforward and are reasonable for exchanges that don't keep going long.

Be that as it may, if the exchange takes additional time, lines can develop rapidly, when Client A beginnings an exchange with the server, Client B can't make a call until A has wrapped up.

In this way, for extensive exchanges, an alternate kind of server is required — the simultaneous server, Here, Client A has just settled an association with the server, which has then made a youngster server procedure to deal with the exchange. This permits the server to process Client B's solicitation without trusting that An's exchange will finish. Beyond what one youngster server can be begun along these lines. TCP⁄IP gives a simultaneous server program called the IMS™ Listener.

Some idea on on time synchronization is Synchronization of Clocks: Software-Based Solutions

Techniques:

1.time stamps of real-time clocks

2.message passing

3. round-trip time (local measurement)

4.Cristian’s algorithm

5.Berkeley algorithm

6.Network time protocol (Internet)

A system time server isn't something numerous entrepreneurs consider, and timekeeping is generally not a need for organize executives. In any case, legitimate system time synchronization is a fundamental piece of checking a system and settling issues inside it.