With the official 1.0 version of ADC, it was decided that a new project for managing ADC would be best. So, we’ve set up The ADC Project, designed to help developers see the documentation and let the community form the future ADC specifications.
(It’s also good to seperate ADC from DC++, as it was previously a “DC++” thing, seeing as the protocol resided on the DC++ space.)
Don’t forget that you can make topic suggestions for blog posts in our “Blog Topic Suggestion Box!”
The new version of DC++ is out ( probably the last one in 2007 ). You can find it here .
As in a previous blog post, this new version adds the Coral distributed network hublists, which will make sure you have a working hublist in your client.
Also, this version brings ( more or less ) the compatibility with ADC 1.0 . This means that the protocol BASE feature is advertised ( instead of the BAS0 revision ). UCMDs ( the ADC’s User commands extension ) is also advertised in the initial SUP string protocol, so DC++ users can now use the commands given by ADC hubowners ( hubsofts should start implementing ) . This also means that 0.704 will use the protocol string ADC/1.0 when trying to download. Don’t worry, you can still download from older versions because the 0.10 protocol string is still kept ( same goes about the INF flags OP, RG… ). The only compatibility that is really breaked is the password sending because the hash the client must send in 1.0 is slightly different ( see differences between ADC 1.0 and 0.10 ).
0.704 includes more fixes that everybody wanted to have as soon as possible, these include : closing tabs with mid-mouse button, chat focusing all the time, hub name printed to main window title.
The segmented downloading crashes are now fixed .
On top of all, enjoy your new version.
After years of more or less active deliberation, it is finally time for 1.0. You’ll find it in the usual place, and differences from 0.14 can be seen here. Some of the extensions have been moved here since they either didn’t have any working implementations (that I know of) or were not finished. The long term plan is to set up a separate sf.net project for the ADC spec were people will be able to propose new extensions in an ordered manner (so that they don’t clash, are well documented and actually exist). Extensions will be added to the main spec as they become mature enough, subject to some procedure that I still have to think about (setting up a voting system would be nice, but it would require N active participants…). With a separate project, I also hope that more non-dc++ people will be interested to contribute…
Oh well, enough rambling, enjoy!
