Big Muscle

ah, I thought he means that if Apex supports Kademlia, it will be possible to use eMule to search Apex's files :)

RevConnect's Kademlia and eMule's Kademlia aren't compatible.

there's protocol limitation -> max 5 results for passives and max 10 results for actives

but there's 50% possibility that you will never get a slot )

but it's not true$. DC++ pseudoqueue is very bad, because you can wait 2 years and you don't get a slot and some user can wait 2 seconds and will get a slot.

better you should say that this is the greatest problem in your PC. ApexDC++ saves its queue correctly, but if your computer doesn't manage to save it, then it's not our problem. if you cannot use them, then it can't be available to others.

This doesn't seem to be Vista problem. Apex just calls some Windows function exported from ntdll, but calls it with invalid parameters or in incorrect time (for example, for resource which has already been deleted from memory etc.) and the second case is what it should be ;-)

it's not needed. Program doesn't allow downloading corrupted files... due to TTH.

via dcppboot.xml :crying:

no, but it doesn't matter, because limit is shown also in emulation mode

there will be no reason to have emulation in the future, because current DC++ SVN supports segmented downloading ;-)

wtl 8.0 and stlport 5.2 are much older than we use

I have the same opinion. There shouldn't be any emulation at all and I'm going to remove it in the future. Only some stupid hubs don't allow our client and emulation is there only for reason to show them we are not stupid as themselves and we can get in their hub also if they forbid it. If emulation will be removed in the future, it will be only good. These stupid hubs will lose a lot of users and it's only their problem ))

There's no such feature. And why? Because this is sharing application. So we will upload to anyone and not "I will upload only to users I want to" ;)

you can't find them by time stamp. For example, today I can download some file which is very long time in the network. And you will see it as a new file in my filelist. Also, i can take in account that Total Commander allows timestamp change :blushing:

I know where the problem is :)

but slow hashing influences only local user... and large filelist influences all users in network

Filelist will be bigger than it's normal. And file timestamp has no real meaning. For filelist with 10 000 files, it will increase about 80 kB and it's much! Filelist must be as small as possible.

it's not good idea because: a) it will be compatible only between clients which support it it will increase filelist size many many times

I just guess that the icon is only in 24bit color format without alpha channels.

I don't think that search in Hebrew will work. Current protocol doesn't support unicode and it also depends on remote side if it has Hebrew support.

it's "feature" of Vista that it doesn't allow writing to "Program files" folder

it just means only one - you did more searches... and one search window filters out the results which don't belong to it

:blink: there aren't... yes, there are implementations which almost work, but it's very easy to break it.

try it