You have to send $ValidateNick first. Look at the bottom of this page:
http://www.1stleg.com/Download/Document ... Login.html
Search found 27 matches
- 2003-06-04 02:57
- Forum: Other Direct Connect tools
- Topic: C# Version
- Replies: 6
- Views: 5005
If you're interested in a DC client written in C#, you could monitor my little project.. In a few weeks, there should be at least a really early Alfa version released. If enough people seems to be interested, I might get to it even earlier..
http://sourceforge.net/projects/dcsharpen
http://sourceforge.net/projects/dcsharpen
- 2003-05-20 05:27
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
- 2003-05-08 02:35
- Forum: Protocol Alley
- Topic: Read/send buffer size
- Replies: 3
- Views: 2735
Thank you for the answers! :D So, the best way might be to give the user a choice of some predefined buffer sizes and let him/her find the one that fit the best? 16k 64k 256k 512k ? What about drive read/write buffers? Should they simply be in sync with the network buffer, or are there other things ...
- 2003-05-02 04:42
- Forum: Protocol Alley
- Topic: Read/send buffer size
- Replies: 3
- Views: 2735
Read/send buffer size
Hi.. I've been trying to google around for some information about how to set buffer sizes when sending/receiving files etc over TCP. However, I only tend to find really complicated algorithms, but what I really need is a few guidelines. I'm guessing the size should be somewhere in the interval 4k-64...
- 2003-05-01 09:56
- Forum: Protocol Alley
- Topic: DC Protocol Guide (Complete)
- Replies: 14
- Views: 8622
First of all, thank you for the doc, it's great! A few comments though (all in Client2Client): There is no need to re-$Send after 40906 bytes. I don't really like the fixation with what goes in what packet. E.g. The $Lock is sent immediately after the $MyNick command within the same packet ... After...
- 2003-04-25 14:07
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 25825
- 2003-04-24 08:34
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 25825
- 2003-04-23 11:26
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 25825
- 2003-04-22 13:40
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 25825
- 2003-04-22 01:32
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 25825
- 2003-04-21 10:49
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 25825
- 2003-04-18 11:21
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
- 2003-04-18 11:08
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
I think you're sort of missing the point (or maybe I am..). The $Cancel command should _never_ be sent by the uploader - i.e. there is no risk of the command beeing sent in the middle of a file stream. The flow would be like this: D>U: $Send U>D: file stream [D saves to disk and doesn't care about a...
- 2003-04-15 08:10
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
Well.. the uploader should never be able to send the $Cancel (or $Canceled) message, that would be reeally bad. However, I still don't see what's soo bad about the downloader sending a message while receiving data? But, I have to admit that I'm not that experienced with socket programming, so maybe ...
- 2003-04-14 13:19
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
Why is $Cancel is a bad idea… When transferring a block of data, the block should be a predefined size. Let’s say 64k. If $Cancel is used by the downloader to tell the sender that it's reached the end of the block, chances are that more that 64k of data would have been sent. This is a ...
- 2003-04-14 12:21
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
Well, after the downloader has sent $Cancel, I guess it should simply discard any further packets, and just look for $Canceled.. I still haven't been able to reproduce this behaviour though, but I'm trying to do it between my own client and NMDC, so I guess I'm doing it the wrong way.. :-( I know, ...
- 2003-04-14 06:23
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
$Cancel will not make it to DC++, it's a stupid and meaningless way of doing things. DC++ does receive during send, but silently ignores what's sent in most cases. Just a bit curious, why is $Cancel such a bad command? I agree that it may not be the best way of handling multiple source downloads, b...
- 2003-04-13 14:09
- Forum: Protocol Alley
- Topic: Compleate DC Protocol Documentation
- Replies: 11
- Views: 21488
- 2003-04-13 14:06
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
This is not good. Tcp streams are just that: streams. You should never rely on packet boundaries. Say the file actually consists of "$Canceled" repeated 10000 times, this makes it hard to know which one is actually a command, and not data. Well, after the downloader has sent $Cancel, I guess it sho...
- 2003-04-13 11:12
- Forum: Protocol Alley
- Topic: Compleate DC Protocol Documentation
- Replies: 11
- Views: 21488
First of all, thank you very much for this documentation! It's great! Second, I wonder whether I can find a similar documentation of all (or some) extensions made to the protocol? I know DC++ has quite a few features that aren't mentioned in the document above, and I suppose there are a few hubs out...
- 2003-04-13 11:03
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
And thanks (!!!) for the pointer about $Cancel (strings on the OSX version turns that up, not $Cancelled). I'm still trying to track down NeoLite for decompressing the win32 NMDC. Apparently they were gobbled up by MacAfee a while back... Well, it seems like we could forget about using that command...
- 2003-04-13 08:01
- Forum: Protocol Alley
- Topic: dcgui & $Supports CHUNK
- Replies: 40
- Views: 18954
Disconnecting when you get a chunk from a file (like pDC does) is borderline abusive, in my opinion. A protocol extension, in $Supports, is the proper way to do this, since the DC protocol doesn't have support for cancelling a transfer in progress. According to the Direct Connect Protocol Documenta...
- 2003-04-09 08:53
- Forum: Protocol Alley
- Topic: Slot notification inefficent
- Replies: 7
- Views: 3986
A similar idea has been proposed here:
http://dcplusplus.sourceforge.net/forum ... php?t=1381
I'd really like this feature too, it would make the DC network just a bit more fair. It should, in my opinion, be implemented the way "sarf" proposes, using "reverse connecting".
/Anders
http://dcplusplus.sourceforge.net/forum ... php?t=1381
I'd really like this feature too, it would make the DC network just a bit more fair. It should, in my opinion, be implemented the way "sarf" proposes, using "reverse connecting".
/Anders
- 2003-04-07 06:41
- Forum: Protocol Alley
- Topic: Client <-> hub handshake.
- Replies: 6
- Views: 3695
Wow! I did the exact same thing when I did the Key->Lock algo in my C# client.. Sorry I didn't read the forum in time to help you out..Moch wrote:Code: Select all
... //NOT 10 because count++ ...
/Anders
- 2003-03-16 07:14
- Forum: Protocol Alley
- Topic: Different users with same nick (but in different hubs)
- Replies: 1
- Views: 1789
Different users with same nick (but in different hubs)
Hi.. just trying to write my own client (aren't we all?..), and I've got a question about how DC++ handles the following scenario.. I must admit i didn't dig through the source code, so I might have gotten the whole download-queue, client-connections process wrong.. The client is connected to two di...
- 2003-02-28 13:06
- Forum: DCH++ General
- Topic: DCH++ in test
- Replies: 36
- Views: 23338
i noticed that dch++ is not as forgiving the client2hub handshake as the nmdc-hub is.... ;)) You're not the only one.. I'm trying to create my own client, in C#, and I just couldn't figure out why I only came halfway through the handshaking, then I realized I sent an extra space after the $GetNickL...