aMule Forum
English => Feature requests => Topic started by: gav616 on March 02, 2008, 03:43:18 AM
-
IsClientCryptLayerSupported=1
IsCryptLayerRequested=0
IsClientCryptLayerRequired=0
should be that at first run, requested obfuscation by default wastes bandwidth if you don't need it.
-------------
gui options for
DisableKnownClientList=
DisableQueueList=
could be under a "save memory and cpu" header..
edit** even with these on 0 they seem to be still enable for me :S using 12 feb svn build
-------------
some were (gui or .ini) to disable udp server requests like in emule
-
With regards to the second request, those options do nothing, and are really not needed. If you don't wish to use the known/queue/uploading lists, just hide it. Only the currently active list is kept in memory, if any is active.
-
IsClientCryptLayerSupported=1
IsCryptLayerRequested=0
IsClientCryptLayerRequired=0
should be that at first run, requested obfuscation by default wastes bandwidth if you don't need it.
What bandwith? Only key exchange and padding, which is actually absorbed by the MTU.
-
IsClientCryptLayerSupported=1
IsCryptLayerRequested=0
IsClientCryptLayerRequired=0
should be that at first run, requested obfuscation by default wastes bandwidth if you don't need it.
What bandwith? Only key exchange and padding, which is actually absorbed by the MTU.
o rly? i just got the impression from the emule faq/forums that if your actively requesting obfuscation but not really needed it there will be unnecessary overhead. (altough from what you have said its very very little)