Warning:
JavaScript is turned OFF. None of the links on this page will work until it is reactivated.
If you need help turning JavaScript On, click here.
This Concept Map, created with IHMC CmapTools, has information related to: ch4 inte clie, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? RPC exchange protocols: request, request reply and request reply acknowledge reply, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? history when a client process terminates it does not acknowledge the last reply it has received, messages in the history are deleted after a certain time period to avoid memory limitations, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? message contents: the name of a method, a URL resource, the protocol version, some headers and an optional message body, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? discarding duplicate request messages: the protocol is designed to recognize extra messages from the same client, with the same request identifier, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? HTTP methods: GET, HEAD, POST, PUT, DELETE, OPTIONS and TRACE, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? timeouts when dooeperation returns it will indicate to the client by an exeception that no result was received, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? HTTP an example of a request reply protocol: content negotiation like porn sites, authentication credentials and challenges are used to support passworld style authentication, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? use of TCP streams to implement the request reply protocol: deciding on the right memory size for buffers, streams are considered since they can be unusually large in size, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? failure model of the request reply protocol: in UDP datagrams they suffer from omission failures and messages are not guaranteed to be received in sender order, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? message identifiers: requires that each message has a unique message identifier by which it may be referenced, a request id and an identifier for sender process, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions ???? lost reply messages: idepotent operations are used to be performed repeatedly with the same effect as if it had been performed exactly once, Client server communication: this form of communication is designed to support the roles and message exchanges in typical client server interactions includes the request reply protocol: matches request with replys, it may be designed to provide certain delivery guarantees