Difference between revisions of "Webcache"
From AMule Project FAQ
| Line 9: | Line 9: | ||
The idea began on 13 April 2003 at [http://forum.emule-project.net eMule's forums] when [mailto:sufcrusher@zonnet.nl sufcrusher] posted [http://forum.emule-project.net/index.php?showtopic=14768 this post]. The history can be followed there up to the first [[eMule]] mods implementing it. | The idea began on 13 April 2003 at [http://forum.emule-project.net eMule's forums] when [mailto:sufcrusher@zonnet.nl sufcrusher] posted [http://forum.emule-project.net/index.php?showtopic=14768 this post]. The history can be followed there up to the first [[eMule]] mods implementing it. | ||
| − | == Pros and cons == | + | == Pros and cons, as seen by the Team == |
=== Pros === | === Pros === | ||
| Line 20: | Line 20: | ||
* Since all your data (or some of it) would pass through your ISP's proxy, your ISP would know what you are sharing, so your privacy would suffer greatly. | * Since all your data (or some of it) would pass through your ISP's proxy, your ISP would know what you are sharing, so your privacy would suffer greatly. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* If you encrypt your traffic then you can't use webcache anyways. Encrypting e.g. with the openssl library like https or ssh does would mean an extension to the edonkey protocol but that should be possible with backwards compatibility. | * If you encrypt your traffic then you can't use webcache anyways. Encrypting e.g. with the openssl library like https or ssh does would mean an extension to the edonkey protocol but that should be possible with backwards compatibility. | ||
| − | |||
* It is not clear whether using ISPs' web proxies for things other than web data is legal. Even if it was in your country, legislation are different from state to state, so [[client]]s try to conform to the broadest possible range of legislation to keep their users from having unpleasant experiencies with the law. Also, allthough the webcache feature might be better for your ISP, it can be bad if the traffic is too high, so you might have your ISP breaking the contract with you and leaving you without connection. | * It is not clear whether using ISPs' web proxies for things other than web data is legal. Even if it was in your country, legislation are different from state to state, so [[client]]s try to conform to the broadest possible range of legislation to keep their users from having unpleasant experiencies with the law. Also, allthough the webcache feature might be better for your ISP, it can be bad if the traffic is too high, so you might have your ISP breaking the contract with you and leaving you without connection. | ||
| − | |||
| − | |||
* Like it or not, webcache at large scale becomes a DDoS to the ISP's http cache servers. The ISPs' clients will notice a worse quality of the service, and ISPs will blame the webcache, being right. What's worse: [[P2P]] developers that support webcache could be sued for developing DDoS tools and invite people to use it, ISPs can say they are losing clients because of the quality the lost in their services, and so, [[P2P]] developer teams could have big problems. | * Like it or not, webcache at large scale becomes a DDoS to the ISP's http cache servers. The ISPs' clients will notice a worse quality of the service, and ISPs will blame the webcache, being right. What's worse: [[P2P]] developers that support webcache could be sued for developing DDoS tools and invite people to use it, ISPs can say they are losing clients because of the quality the lost in their services, and so, [[P2P]] developer teams could have big problems. | ||
| − | |||
| − | |||
* The [[P2P]] networks are being heavily tracked by some governments since they believe they are used for illegal purposes. There is a popular saying: "if it works, don't touch it". Well, that applies it here. | * The [[P2P]] networks are being heavily tracked by some governments since they believe they are used for illegal purposes. There is a popular saying: "if it works, don't touch it". Well, that applies it here. | ||
| − | |||
== Implementing webcache == | == Implementing webcache == | ||
| Line 49: | Line 38: | ||
Anyway, until further (and highly unlikely) news, neither [[aMule]] nor [[eMule]] are going to officially support webcache in any future release. | Anyway, until further (and highly unlikely) news, neither [[aMule]] nor [[eMule]] are going to officially support webcache in any future release. | ||
| + | |||
| + | '''This topic is NOT open for discussion.''' | ||
Revision as of 22:46, 15 February 2005
Contents
Description
The idea of webcache is to upload the shared data into an ISP proxy and leave it there for other clients to download.
The description of the scheme can be found with full details in the original post. Plus, there are lot's of additional documentation pages all around the net; Google is your friend ;)
History
The idea began on 13 April 2003 at eMule's forums when sufcrusher posted this post. The history can be followed there up to the first eMule mods implementing it.
Pros and cons, as seen by the Team
Pros
- The most evident pro, and the main purpose of it, is that web proxies have a lot of bandwidth and very high speed so the data sharing speeds should be greatly boosted.
- Also, P2P clients generate heavy traffic on ISPs since they open and close lots of connections in very little time and send/receive large amounts of data. Using webcache would stop these connections from going through the ISPs since they would only get to the ISPs' proxies.
Cons
- Since all your data (or some of it) would pass through your ISP's proxy, your ISP would know what you are sharing, so your privacy would suffer greatly.
- If you encrypt your traffic then you can't use webcache anyways. Encrypting e.g. with the openssl library like https or ssh does would mean an extension to the edonkey protocol but that should be possible with backwards compatibility.
- It is not clear whether using ISPs' web proxies for things other than web data is legal. Even if it was in your country, legislation are different from state to state, so clients try to conform to the broadest possible range of legislation to keep their users from having unpleasant experiencies with the law. Also, allthough the webcache feature might be better for your ISP, it can be bad if the traffic is too high, so you might have your ISP breaking the contract with you and leaving you without connection.
- Like it or not, webcache at large scale becomes a DDoS to the ISP's http cache servers. The ISPs' clients will notice a worse quality of the service, and ISPs will blame the webcache, being right. What's worse: P2P developers that support webcache could be sued for developing DDoS tools and invite people to use it, ISPs can say they are losing clients because of the quality the lost in their services, and so, P2P developer teams could have big problems.
- The P2P networks are being heavily tracked by some governments since they believe they are used for illegal purposes. There is a popular saying: "if it works, don't touch it". Well, that applies it here.
Implementing webcache
There are already some clients out there supporting webcache. Most of them are eMule mods. We do NOT recommend using them. These mods bring down the P2P reputation and by using them you contribute in doing so.
Regarding aMule
Discussions about implementing webcache feature into aMule have appeared many times in aMule's forums although maybe the most relevant is this one.
Anyway, until further (and highly unlikely) news, neither aMule nor eMule are going to officially support webcache in any future release.
This topic is NOT open for discussion.
