{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}


Some communicaon events are unicast ie from one single

Info icon This preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: s the precise sequence of events that must be enacted by the communica=ng processes for them to engage in communica=on and exchange informa=on. Some communica=on events are unicast (i.e., from one single process to another single process), some are mul/cast (i.e., from one single process to many other processes). Protocols Use IPC API Calls 4 ws:t13:accept web server wb:t14:connect ws:t25:receive(request) wb:t27:send(request) web browser wb:t30:receive(response) ws:t31:send(response) ws:t48:disconnect wb:t47:disconnect Synchroniza=on 5         (Recall, no global clock!) Timestamp t in the web server may be later in real =me than =mestamp t’ in the web browser even though t’ < t. If so, i.e., then if the web browser Send has no Receive counterpart in the web server, data may not be exchanged. One way to avoid this is for:     The web browser in its turn to issue a synchronous Send, i.e., one that waits un=l comple=on, and The web server to keep polling (looping around the Receive). TCP IPC 6 [8] … message exchange … h’ h [2’’] p...
View Full Document

{[ snackBarMessage ]}