Webcache - Revision history

Omeringen at 20:14, 6 May 2010

2010-05-06T20:14:10Z

Leuk he: /* Criticism */

2007-06-05T14:35:24Z

Criticism

Awaw: added sections about advantages, criticism and public proxies; also some minor stuff

2007-04-01T10:09:57Z

added sections about advantages, criticism and public proxies; also some minor stuff

Leuk he: add image

2007-03-21T19:41:59Z

add image

87.205.51.136 at 06:16, 19 March 2007

2007-03-19T06:16:00Z

Leuk he: 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...

2007-03-16T09:07:27Z

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...

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 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:

Image:Webcache2.gif
== See alos

* Official Webcache-Homepage (http://www.ispcachingforemule.de.vu)

[[category:features]][[Category:stullemulefeatures]][[Category:Morphxtfeatures]]

← Older revision		Revision as of 20:14, 6 May 2010
Line 38:		Line 38:
	* [[Peercache]]		* [[Peercache]]

−	[[~~category~~:~~features~~]][[Category:~~stullemulefeatures~~]][[Category:~~Morphxtfeatures~~]]	+	[[Category:Features]][[Category:StulleMule features]][[Category:MorphXT features]]

← Older revision		Revision as of 14:35, 5 June 2007
Line 28:		Line 28:

	Furthermore it is discussed if the relatively little chance to get a match (chunk, time etc., see public proxies section) is worth the effort.		Furthermore it is discussed if the relatively little chance to get a match (chunk, time etc., see public proxies section) is worth the effort.
		+
		+	=== Abandoned ===
		+
		+	Since 0.48a most major mods do not support webcache anymore. Users who still want to use this have to use older versions.

	== See also ==		== See also ==

@@ Line 1: / Line 1: @@
-Webcache
+Webcache is a technology which should help reducing network load and increase download speed by caching the download data at a proxy.
-Webcache Options
-Enlarge
-Webcache Options
-[image:http://wiki.emule-web.de/image/Webcache2.gif]
+== Method ==
-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:
+There are eMule users S, A, B, C on the net. Users A, B, C are using the same proxy 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.
 == See also ==
 * Official Webcache-Homepage (http://www.ispcachingforemule.de.vu) NOTE: Dead?
 [[category:features]][[Category:stullemulefeatures]][[Category:Morphxtfeatures]]

← Older revision		Revision as of 06:16, 19 March 2007
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: