Search found 22 matches
- 2003-07-28 09:27
- Forum: Protocol Alley
- Topic: types of filelists
- Replies: 7
- Views: 4963
- 2003-07-07 16:14
- Forum: Protocol Alley
- Topic: Key calc problems
- Replies: 4
- Views: 3106
Your code generates the same keys as mine, and I get the same small errors, I really wonder what the reason could be, especially if it works on your pc... In that case, it's probably a problem with your character encoding. You should be using the default encoding, ie. System.Text.Encoding.Default, ...
- 2003-07-07 00:24
- Forum: Protocol Alley
- Topic: Key calc problems
- Replies: 4
- Views: 3106
Mine. Tested and it works. /// <summary> /// Computes the $Key respnse to a given $Lock command. /// </summary> /// <param name="lockStr">The Lock string in the middle of "$Lock (.*) Pk=".</param> /// <param name="xorKey">0x05 for a connection from a client to a hub, /// or (localPort+(localPort>>8)...
- 2003-05-26 03:37
- Forum: Protocol Alley
- Topic: Why Multiple Compression Protocols?
- Replies: 2
- Views: 2345
See this thread: Upcoming: ZLib block compression.
- 2003-04-25 18:51
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 27268
- 2003-04-24 04:41
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 27268
- 2003-04-24 01:14
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 27268
Well OK then. :) Same priviso as above; mail me if you find any bugs. /// <summary> /// Class for compressing NMDC file lists. /// </summary> /// <remarks> /// Written by Paul Bartrum (paulbartrum@hotmail.com) /// </remarks> public class NMDCHuffmanCompressor { class HuffmanCompressionNode { public ...
- 2003-04-23 00:36
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 27268
- 2003-04-21 20:06
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 27268
Since you asked so nicely, here's my huffman decoder. :) It's written in C# and IIRC has been tested and verified as working. YMMV. If you find any bugs please contact me. /// <summary> /// Class for decoding NMDC file lists (of the form MyList.DcLst). /// Encoding is not supported. /// </summary> /...
- 2003-04-08 16:21
- Forum: Protocol Alley
- Topic: Could somebody please explain the decryption algorith?
- Replies: 23
- Views: 11115
The problem is definately the character encoding. You may not realize this, but you are doing at least 2 character encoding conversions. 1: UTF8.GetBytes() (converting the lock string to a byte array) 2: Your network send code (converting the key string to a byte array) You need to use the character...
- 2003-04-07 22:06
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 27268
- 2003-04-05 19:59
- Forum: Protocol Alley
- Topic: Client <-> protocol questions
- Replies: 33
- Views: 27268
You know huffman coding? Here are the details for the neomodus variant: byte offset / description 0 = "HE3" (magic bytes) 3 = 13 4 = checksum (XOR of every byte in the uncompressed file) 5 = length of uncompressed file 9 = number of entries in following table 11 = entry 1 [uncompressed byte, compres...
- 2003-02-02 18:15
- Forum: Protocol Alley
- Topic: Compleate DC Protocol Documentation
- Replies: 11
- Views: 21508
- 2003-01-26 18:35
- Forum: Protocol Alley
- Topic: Adding file hashes to the protocol
- Replies: 97
- Views: 46108
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? If clients don't send the hash value in search results then there is no (practical) way to automatically group search results, ala KaZaA, eDonkey, etc. This is a de...
- 2003-01-24 02:51
- Forum: Protocol Alley
- Topic: Client->Client question
- Replies: 13
- Views: 6602
Does client->client lock2key algoritm is the same as in client->hub ? (still xor byte = 5 ?) Yes. I maybe mistaken but I belive there is no direct client to client protocal it all goes through the hub You're mistaken. :!: Just after connecting to another client (for downloading) the one downloading...
- 2003-01-21 07:09
- Forum: Protocol Alley
- Topic: Adding file hashes to the protocol
- Replies: 97
- Views: 46108
- 2003-01-20 20:47
- Forum: Protocol Alley
- Topic: Optimized search
- Replies: 5
- Views: 4064
- 2003-01-17 21:17
- Forum: Protocol Alley
- Topic: Standard listening port for file download?
- Replies: 2
- Views: 2501
- 2003-01-17 05:18
- Forum: Protocol Alley
- Topic: Adding file hashes to the protocol
- Replies: 97
- Views: 46108
IMHO, if we ever want the ease-of-use features of, say, KaZaA in DC, we need to implement file hashes. The following features spring to mind: * Automatic grouping of search results. * Automatic finding of new sources. * Working hyperlinks to DC files (rather than just hubs). * Automatic redownloadin...
- 2003-01-16 22:48
- Forum: Protocol Alley
- Topic: Adding file hashes to the protocol
- Replies: 97
- Views: 46108
Adding file hashes to the protocol
OK, I think most people here agree we should add file hashing to the DC protocol, especially given that the vast majority of p2p systems have it already. Note that none of the proposed solutions require any changes to the hub. We could do a lot better if we mandated changes to the hub, but for pract...
- 2003-01-15 23:48
- Forum: Protocol Alley
- Topic: Time to write a complete RFC.
- Replies: 28
- Views: 12912
- 2003-01-15 23:46
- Forum: Protocol Alley
- Topic: DCExt..
- Replies: 11
- Views: 5876
Excellent! This is just what we need!
One thing that occurs to me though is how do the clients know that this extension is available? Perhaps you should include the QuickList spec as part of your document (I assume Nev won't mind): http://forum.dcstats.net/showthread.php?s=&threadid=802
One thing that occurs to me though is how do the clients know that this extension is available? Perhaps you should include the QuickList spec as part of your document (I assume Nev won't mind): http://forum.dcstats.net/showthread.php?s=&threadid=802