Explain the Client-Server Interaction Using Messages
As we have learned, client- server interaction may be managed in many ways. A message- based interaction is perhaps the best choice for many reasons. It turns out that applications architected specifically for client-server may be optimized with the processing of client server messages and by the facilities used to manage the message. As such, the message-based interaction for client -to-server interaction is becoming a preferred model.
The mechanisms of client-to-server interaction remain relatively similar to the previous example using procedures. Clients make logical request of the server component and expect result returned (either synchronously or asynchronously). Client developers are faced with different method of passing parameters, calling the server, and receiving results. Even with the different semantics, however, creating client-server applications is very straightforward. A message-passing model is employed by many of today's popular driven graphical operating systems. Event loops and action based upon them is the native model for many of these client operating environments. Client- Server interaction should work very similarly. The major difference is that the application components and the message difference is that the application components and the message communication itself may be distributed over the network to a server.