sorry for posting this "request" in this section also - but it looks like the "Protocol Alley" isn't visited so often.
down to the point:
Hi all,
I was wondering since many of us, have different download speeds if we download through a proxy (http cache) if it would be possible to add an option, where you would write besides your connection (socket) proxy, also your download proxy.
For example a lot of users have different limits for traffic inside own country and for foreign country.
Now if I would be able to type a http cache proxy, I would be able to download with limits from my own country, which means 4 times faster transfare in both ways. I think E-Mule has something like this already in it.
Any comments suggestions?? Would that be an option?
I was now browsing a little through DC++ and remembered that it already has support with proxy feature, but just for Public hub lists. Would it be possible to extend that support for every download?
Best regards
download proxy
Moderator: Moderators
-
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-07 21:46
- Location: .pa.us
I don't think it's feasible. DC++ needs to be able to send UDP, and I don't think you can tunnel UDP through a HTTP proxy, which is needed if the entire connection is run though the HTTP proxy. Many pieces of hub software check IP addresses in searches and connection attempts against the IP you're connected through, so tunneling only uploads and downloads will sometimes fail, resulting in potentially large Help/Support issues.
-
- DC++ Contributor
- Posts: 3212
- Joined: 2003-01-07 21:46
- Location: .pa.us
Sorry, but modern hubs should check the IP you connect with, the IP in your $ConnectToMe, and the IP in your $Searches to make sure you're not DoSing a remote computer (as has been done in the past). Doing what you want should not be possible without special dispensation from the hub.dickhead wrote:everything else would remain the same.
I think he was referring to this: http://webcache-emule.sourceforge.net/
Haven't seen it in action myself as my ISP does not run a HTTP proxy.
If it was going to be implemented, the users could use $ConnectToMe to establish a connection as normal, then use that connection to negotiate use of a proxy (using $Supports etc) or just transfer over that connection if proxying is not supported at both ends.. Also hub writers could implement a $Support so the proxying can be negotiated over the hub. (to save wasting a new connection).
Haven't seen it in action myself as my ISP does not run a HTTP proxy.
If it was going to be implemented, the users could use $ConnectToMe to establish a connection as normal, then use that connection to negotiate use of a proxy (using $Supports etc) or just transfer over that connection if proxying is not supported at both ends.. Also hub writers could implement a $Support so the proxying can be negotiated over the hub. (to save wasting a new connection).