Webcache
(New page: Webcache Webcache Options Enlarge Webcache Options There are eMule users S,A,B,C on the net. Users A,B,C are using the same ISP and want the same file chunk from user S. They already ente...) |
|||
| Line 6: | Line 6: | ||
There are eMule users S,A,B,C on the net. Users A,B,C are using the same ISP and want the same file chunk from user S. They already entered his queue. Now eMule S sees that there are several (the exact number is discussed) requests. Emule decides to start a http-proxy-upload. It starts a kind of webserver on its TCP-port. | There are eMule users S,A,B,C on the net. Users A,B,C are using the same ISP and want the same file chunk from user S. They already entered his queue. Now eMule S sees that there are several (the exact number is discussed) requests. Emule decides to start a http-proxy-upload. It starts a kind of webserver on its TCP-port. | ||
| − | Now it tells user A to start downloading from http://[IP of user S]/3445467.htm over his proxy. After this is finished, user A starts spreading the http-proxy-source to all users behind the same proxy and needing this filepart. So users B and C get the source and start downloading from the proxy. There's no more upload traffic anymore. I hope this animation makes it more clear: | + | Now it tells user A to start downloading from http://[IP of user S]/encryptedData/28394-152/3445467.htm over his proxy. After this is finished, user A starts spreading the http-proxy-source to all users behind the same proxy and needing this filepart. So users B and C get the source and start downloading from the proxy. There's no more upload traffic anymore. I hope this animation makes it more clear: |
Revision as of 06:16, 19 March 2007
Webcache Webcache Options Enlarge Webcache Options
There are eMule users S,A,B,C on the net. Users A,B,C are using the same ISP and want the same file chunk from user S. They already entered his queue. Now eMule S sees that there are several (the exact number is discussed) requests. Emule decides to start a http-proxy-upload. It starts a kind of webserver on its TCP-port.
Now it tells user A to start downloading from http://[IP of user S]/encryptedData/28394-152/3445467.htm over his proxy. After this is finished, user A starts spreading the http-proxy-source to all users behind the same proxy and needing this filepart. So users B and C get the source and start downloading from the proxy. There's no more upload traffic anymore. I hope this animation makes it more clear:
Image:Webcache2.gif
== See alos
- Official Webcache-Homepage (http://www.ispcachingforemule.de.vu)
