637 views
1 votes
1 votes
Primitives of transport service assume asymmetry between the two end points during connection establishment, one end (server) executes LISTEN while the other end (client) executes CONNECT. However, in peer to peer applications such file sharing systems, e.g. BitTorrent, all end points are peers. There is no server or client functionality. How can transport service primitives may be used to build such peer to peer applications?

1 Answer

0 votes
0 votes

Answer: In this case, as the peers are the two endpoints, so a separate mechanism is required that tells the endpoints at run time that which end will represent as server and which will represent as a client, including their addresses.

We can achieve this by having a different coordinator process that gives this information to the two endpoints before the connection between them is established.

Related questions

0 votes
0 votes
0 answers
1
0 votes
0 votes
0 answers
2
1 votes
1 votes
2 answers
3
1 votes
1 votes
1 answer
4
ajaysoni1924 asked Mar 18, 2019
840 views
In Fig. 6-36 we saw that in addition to the 32-bit acknowledgement field, there is anACK bit in the fourth word. Does this really add anything? Why or why not?