Problem identifying Descriptor IDs
 

One question regarding Descriptor IDs...
How come I get descriptor IDs like ?®ƒCÒ_åA¿1,ëÖçu| from Gnucleus & LimeWire?
When I connect my client with Shareaza I get GUIDs like B4D7F325DA144026,
the type which my client used to send too.

I dont know if the information is important but I'm creating GUIDs with CoCreateGuid
My client (Suicide) is coded in VB 6.0, I made following type.

Public Type descriptor_header
descriptor_id As String * 16 '<- The GUID
payload_descriptor As Byte
ttl As Byte
hops As Byte
payload_length As Single
End Type

Have I forgotten something? Or is the descriptor I get from Gnucleus also valid?

The desperate
Paradog

The descriptor ids are binary so you will (should?) get characters that appear like this ?®ƒCÒ_åA¿1,ëÖçu|
As long as they are mostly unique it really doesn't matter.

You sure?
But I'm sending the Descriptor IDs as a string, and it works.
How come Shareaza sends me non-binary IDs?

Possibly it takes the GUID and converts it to a hex string then takes the first 16 chars . It really doesn't matter as long as it is unique.

Oh right,
Thanks.
Have you read the PM?

By the way, I was wondering how big the possibility is
to have to same GUIDs within a horizon.
I'm not very good at maths (Hey! I'm still in school),
but I guess its (16*36)^16 or am I wrong?

Re: Problem identifying Descriptor IDs
 

Gnucleus has the same thing, and theirs are longer than 16 bytes (32 bytes instead of 16) . It looks like their converting those random characters to hex.