Rigor O'Mortis

An interesting idea would be to have a double client - both a regular one and an "OP" one... since all DCs can detect your "OPness" on every hub, how about if ApexDC will have OP functions that would only be available on the hubs where the user is an OP? The reason behind this idea is that I'd like to stay on more hubs... some on which not necessarily being an OP, and I don't much like the idea of having two DC clients... Also, a separate filelist for every hub would really come in handy...

This request, if you ask me, is a bit on the edge... First off, the same file that you were downloading on one hub could be found on other hubs as well, so the question of where you acquired it first is kind of irrelevant, as long as you have a TTH-based "Search for alternates" Second off, it would be difficult to code in my opinion, but let's say the coders do it. We get to the third issue: what if that person changes the filename / nickname / IP address ? And that same person can be on more hubs at a tiome... and that same person will change its filelist, or another person with the same nickname may enter... thus resulting in a clogged download environment for most of us who do not wish to bother with such rigurous download space. So... what is that facility useful for exactly ?

I offer my full help for translating it in Romanian and Hungarian, when Apex will be out in final version...

Ther compatibility with older CRT functions can be reactivated in VS2005, in order to compile properly. In any case, using the new *_s functions is recommended, if possible to port the code accordingly. It works, but you have to eliminate some ooky errors and two or three idiotic ambiguous definitions... Or you can just use the pre-compiled version... I'm playing with the source code of DC++ 0.687 right now... It's kinda` nice to look at... Can't wait to see how StrongDC RC11 will perform... And ApexDC, well... I did promise to build a hub specifically for ApexDC users...

Now THAT would be a VERY VERY nice idea... good thinking... it would also apply to accidental disconnects from your ISP (which I, for instance, have a lot). Since we're speaking of Zion++, I'd also like to request a little feature... I've seen how PeerWeb DC++ works when using usercommands, and how Zion++ uses them. The difference is that PeerWeb DC++ takes a whole lot more time to execute them... for instance, if you use a usercommand to send private messages to other users, it's almost as if PeerWeb DC++ was waiting for an echo from them... the more users you applied the usercommand for, the more time PeerWeb DC++ was remaining in a "Not responding" state. I suggest you attempt to correct that, it's really difficult for an OP to use his/her usercommands this way. 100 users means 2 minutes of waiting on a 256k connection. Next, about the connection page... I do hope it's not difficult to make another container saying "Advanced connection settings" inside that "Incomming connections (see help/faq if unsure)" where to place all those "extra" features. An auto-update IP every x minutes, where x is selectable by the user, and by default 60 minutes, would really come in handy sometimes. Another feature that I'd like added would be the ability to scan all tags for fake clients / limiting / etc. every X minutes... that would, I believe, make ApexDC++ one of the strongest clients available.