ADC vs NMDC
From ADC Project
This section intend to list the differences between the ADC and DC protocol. However, note that this compromised of features in ADC 1.0 and the, as of December 2007, implemented DC protocol.
| Protocol | Description |
|---|---|
| ADC | An actual official specification that clients must follow |
| ADC | Token in search results and client-client connections. |
| ADC | Referring URI when client is redirected |
| ADC | A kicked client's transfers can be forcefully terminated by other users. |
| ADC | A global identification scheme is possible. |
| ADC | Out-of-the-box IPv6 support. |
| ADC | Defined character esape sequence. |
| ADC | Defined character encoding and normalization. |
| ADC | Salted passwords during hub-client negotiation. |
| ADC | Defined amount of search results per client mode (active and passive). |
| ADC | Required that hubs and clients support hashes. |
| ADC | Incremental client information. |
| ADC | Searching for a file type does not depend on the remote client. |
| ADC | Functionality for speaking in third person. |
| ADC | Protocol delimiters: "\\", '\n' and ' ' (space) |
| ADC | No port default |
| ADC | Token determine download priority |
| NMDC | The non-use of ' ' (space) as a delimiter, allowing less bandwidth for hub chat. |
| NMDC | Protocol allowing, out-of-the-box, kicking and redirecting users from a client perspective. |
| NMDC | ", '$' and ' ' (space) |
| NMDC | Port default is 411 for hubs and 412 for clients. |
| NMDC | "Highest random number" determine download priority |
