Hi all. How about to add a new feature - 'IP Resolving'?

You mean resolving so one can see the hostname?

I guess he do, but for what use ?, it will only slow KT down a **** lot if it has to perform a rDNS lookup

Jesper wrote:I guess he do, but for what use ?

To be pretty And some more info is known from DNS name than from IP.

Jesper wrote:, it will only slow KT down a **** lot if it has to perform a rDNS lookup

Well, I guess most peers are stable for a period of time, it can rDNS only once and cache the results...

If implemented, it can be disabled by default and when trying to enable a popup would appear saying it will generate more traffic...

i23098 wrote:

Jesper wrote:I guess he do, but for what use ?

To be pretty And some more info is known from DNS name than from IP.

Jesper wrote:, it will only slow KT down a **** lot if it has to perform a rDNS lookup

Well, I guess most peers are stable for a period of time, it can rDNS only once and cache the results...

If implemented, it can be disabled by default and when trying to enable a popup would appear saying it will generate more traffic...

LOL to be pretty, I like that reason NOT !!!

A cache might be a good idea, but it will be HUGE if you have a lot of peers/torrents running, and KT eat your CPU big time when it has to check if the address is already in that list before it performs a lookup.

Last of your ideas would have to be a must cause people that don't know would enable it and complain about the CPU usage

Finally... who the hell gives a D. about the hostname of the IP... unless some feature to ban hostnames with wildcards were implemented too

Jesper wrote:unless some feature to ban hostnames with wildcards were implemented too

Now that you mention it... A good idea (besides yours ) would be to boost the preference of peers that are within some hostname wildcard.

Traffic within my ISP's network doesn't count to the download limit, so it would be a good idea to prefer those peers, or ban all others except between 0:00am and 6:00am (happy hour all traffic does not count). Similar to bandwidth scheduler but using DNS with wildcards...

I dont think it is up to KT to decides which peers are sent to you from the tracker, so that idea is probably shot dead before you even thought of it

The IP/Hostname ban should be an easy implement tho, most if not all FTPdaemons supports bans on Hostnames or IP ranges, so I am sure George can implement that for a v3.3 or later 3.x version