DC++

Im not that experienced with corsscompability GUI code but this is how i sloved my corosscompability isse with threads and sockets. I created classes for them and seperated them from what ever project i need them in. The only link bethwine them are the header files. This way nerly all my console app...

No i get it all the time. And the forum in general have been a bit slow latly.

Change the name of the iterator to something else? There is a post about this somewhere else on the forums i think.

OK good to know when i try to make it to complie. Anyoe got it to compile under VC++ 6.0?

Looks like 0.24 not compatibel with VC++ 6.0. Anyone got it to compile using it?

Hum six of them are you sure? i just downloaded the 0.24 src and i can only find five of them... well maybe that explains why i get the same result as zaleth. And yes i have latest SDK and both stlport ad wtlport DC 0.233 compiled just fine. Any idees? but i agree it looks like a project is missing ...

I totaly agre with [A&AM]Fireball. Make a improved protocol and switch to it. I think many developers will switch to it to if it have lots of featurs that the original DC protocol dose not have.

If you don't know what you're talking about, please just lurk and avoid posting unless you know that you're adding something of value. Well i talk about the hypotetical layout of a new protocol not the implantation of it. And i dont think it is significant to argue about what brand of a sulution is...

After you have moved the include paths around always do a make clean befor you try to compile it again else the moved include paths will only effect the files that have not yet been succesfully compiled. And i think the stl port have a new namedecoration to the std components than VC++ default uses....

Public/Privte key eles they can log the key and the encrypion is totaly worthles. Neg, the standard practice is to transfer the key using private/public keysets and then go with symmetric encryption from there on out. Private/public key systems are just too resource intensive. If the various commun...

vanilla_kisses: easy sulution change nick or disconnect from hub?

what is the empty command? i have seen it on my hub/client projects but dont know why it's sent. the | i guess is to tell server/client that the connection is still open.

Take a look at zlib for decompresing or DC++ sourcecode. But i think this tool (if i have understod how it works) is not that usefull. If someone made a fake client wulde they just not block the bypass max slot file list thing? i bet if they figured out how to add to there share that they can in les...

Is there realy a need to provied the hase valut in the search? Is it not easier to transfer the hash in the Client to Client protocol? Just befor a $Send the serving client sends a $Hash or sutch so the reciver know it resumes from a good source. This way no one needs to make a compleat hash list of...

I think the ide of blocking slots is a general bad ide. Because it will lock many slots on many clients after they actulay shulde be free. If a user of some reasin get idsconnected or banned it is moast likly his own fault in some way. I have never been disconnected by chans there is always a reson ...

There is a Pk in the $Lock i did not say there wasnot did i? but there is none in the $Key.

There is no Pk=somepk in the $Key string i think.

Why the hell, do you need Public/Private Key encryption??? At first, such encryption is very resource demanding. So Symmetric key encryption is usually used to transfer great amounts of data. But anyway, I think encryption is of no use in dc++. Anyone can read you filelist so why do you want to enc...

Btw, code is the best documentation, you dont have to explicitly write the docs, and its always current. (Yeah I know its hard to read) Code is not hard to read but its generic bad to use it as development documentation when developing new clients. If the code is bad commented the 2nd developer mig...

Hi The ide of a RFC document is good but i think we need to make some major chnages in the protocole. Insted of adding varius hacks to the NMDC protocole i think we shulde trhow away NMDC compability and rewrite the protocole to support many new feats. Im no big time user of DC++ i use my own home c...