Search the active ADC and the passive NMDC protocol

One of the big culprits in DC traffic is searching. For hub owners, this is a crucial item, as it may make or break their love for either protocol. The less traffic, the more overall users.

So, let us jump right in. I’m going to break this up in two posts. The first post (this) will be about the actual searching, and I’ll later bring up the responses. I’m going to go ahead and begin with active searching and later continue with passive.

NMDC: $Search ip:port F?F?0?1?motd$txt
This is 35 characters. Atleast. (I used single digits in the IP and port. [x.x.x.x:x] Remember that a lot of users aren’t on single digit ISPs. Or are using port 1-9.)

ADC: BSCH BABA ANmotd ANtxt TOsometoken
This is 26 characters. Atleast. (I used a single character for token to come up with 26. The token may vary on implementation. It can be less or more, depending on how many searches one would want to have simultaniously. It’ll probably be less than 10 characters though, but one can’t say that for sure.) Now, this isn’t entirely true, with the 26 characters bit. You see, if you’re an active user you will most likely broadcast your IP and port when connecting. However, as this is done only once, it doesn’t matter much. If we’re going to be picky, it’s 14 additional characters in the INF. (Going by the same rules that I used previously concerning IP and port.)

Moving on to passive searching…
NMDC: $Search Hub:requesternick F?F?0?1?motd$txt
This is 29 characters, excluding the nick. Here again, the length of the nick matter.

ADC: FSCH BABA ANmotd ANtxt TOsometoken
This is (also) 26 characters, and the same rule about the token apply here. Mind you, here, the broadcasting in the INF isn’t performed. But other than that, it’s just a matter of a B for a F.

Comparing NMDC and ADC searching in active mode is definitely a clear win for ADC. The initial broadcasting is forgiveable since it’s only done once and isn’t rippled through the future searches. (It’s up to the clients to keep track of the IP and port.) If we look at passive searching, ADC will remain the same (well, ‘better’ since there’s no initial broadcast), and NMDC wil be slightly better than its active counter part. However, as the nick of the user is important, and is seldom one or two characters, ADC will win here, too.

2 Responses to Search the active ADC and the passive NMDC protocol

  1. Pingback: Search replying in NMDC and ADC « DC++: Just These Guys, Ya Know?

  2. Pingback: ADC Search Types « DC++: Just These Guys, Ya Know?

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: