Generated DC files.xml.bz2 is invalid
Posted: 30 Jan 2013 12:53Hi,
I recently stumbled upon a user on the Direct Connect network whose file list I was unable to open (using ncdc 1.14). The users' client was advertised as "Shareaza 2.6.0.0", and I noticed that there was a bug in the received files.xml.bz2 file. All XML element and attribute names were lowercase, but the spec[1] requires different casing. XML names are case-sensitive.
I've committed a "fix" to the ncdc git repo[2] to accept these lists, but it'd be nice to have this fixed in Shareaza, too.
1. http://adc.sourceforge.net/ADC.html#_file_list
2. http://g.blicky.net/ncdc.git/commit?id=2e4771f
I recently stumbled upon a user on the Direct Connect network whose file list I was unable to open (using ncdc 1.14). The users' client was advertised as "Shareaza 2.6.0.0", and I noticed that there was a bug in the received files.xml.bz2 file. All XML element and attribute names were lowercase, but the spec[1] requires different casing. XML names are case-sensitive.
I've committed a "fix" to the ncdc git repo[2] to accept these lists, but it'd be nice to have this fixed in Shareaza, too.
1. http://adc.sourceforge.net/ADC.html#_file_list
2. http://g.blicky.net/ncdc.git/commit?id=2e4771f