Search replying in NMDC and ADC

I previously wrote about some search statistics in NMDC and ADC. Today’s post is about the actual search replies. As before, I’ll start with active and then move on to passive searching.

Search replies where the person doing the search is in active mode.
NMDC: $SR mynick motd.txt1000 1/1TTH:MIC2BCFKXGQKPFN5WHEKGK7ANAAYUHURCWVRRRY (x.x.x.x:x)|
This rounds up to 80 characters. This may look like a lot, but don’t be frightened. The is a single character. The “x.x.x.x:x” is the hub address and port (where the port can be omitted if it’s 411). I used single digits in both to come up with 80. The nick of the searcher was in my example 1 character. If we’d been in a non-TTH world, the entire TTH bit would be changed to the name of the hub, but that’s unsual today.

ADC: DRES ZB4H P6L5 SI1000 SL1 FN/motd.txt TRMIC2BCFKXGQKPFN5WHEKGK7ANAAYUHURCWVRRRY TOsometoken\n
This is 84 characters with one character as token. Notice that the token is an exact copy of the token sent in the search. TTHs are required in ADC so one can’t avoid them. Of course, we have additional characters in the INF to denote the IP and port of the active user. But they’re only sent once.

In active searching, NMDC have a couple of factors to count in. In ADC, we only have one factor, which in itself probably is rather limited. In any case, it’s quite even between ADC and NMDC.

Now searching where the searcher is in passive mode…
NMDC: $SR mynick motd.txt1000 1/1TTH:MIC2BCFKXGQKPFN5WHEKGK7ANAAYUHURCWVRRRY (x.x.x.x:x)thenickofwhosentthesearch|
This rounds up to 82 characters. Same rules as above. The nick of who sent the search was in my example one character, too.

ADC: DRES ZB4H P6L5 SI1000 SL1 FN/motd.txt TRMIC2BCFKXGQKPFN5WHEKGK7ANAAYUHURCWVRRRY TOsometoken\n
Yes, this is the exact same string. One can send the search reply in other ways, too, but this is what a current DC++ version will send. (Or at least what I could gather from Wireshark.)

This show that there’s even more factors in passive NMDC searching. The token factor in ADC remain (obviously) the same.

In NMDC, the best case scenario is when users have very short nicks and the hub IP is “short” and the port is 411. In ADC, the best case scenario is when the token, the searcher used, is short.

In conslusion, NMDC and ADC are quite close when it comes to search replies. However, as ADC have fewer variables, it has best scaling possibility.

Don’t forget that you can make topic suggestions for blog posts in our “Blog Topic Suggestion Box!”

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: