Re: [Mldonkey-users] directconnect strategy

[b8_bavard]

>  For what I can see, it has been on alpha status for some time now
>  (way too many builds without any changes on dc). I really hope
>  things will change, as this is a very good network (imho) since
>  hubs are theme-specific, so the user won't get xxx files if he
>  doesn't want to.

The problem is that we have had very small feed-back about the DC
plugin in MLdonkey. DC seems to be a network where you have to be in
front of your GUI to interact with it, to follow the downloads, and so
on, which is a bit different from what typical mldonkey users are used
to. In particular, having feedback from an advanced DC user, or even
an old DC programmer would be great to help fixing some problems...

>       In the DC network, you can browse user shared files by
>  downloading a "file list" file from the desired user. I propose we
>  download all file lists automatically as soon as another user enters a
>  hub, and build an overall file list, which we would browse as a complete
>  hub-file list, instead of a per-user file list. This would allow for
>  easier location of files. I believe none of the "official" clients has
>  this feature, but some power-user dc++ modifications have something like
>  this.

   This looks like the kind of features that would make mldonkey even
more welcomed on DC hubs :) I already see all the complains about
every mldonkey client eating the bandwdith of the DC
users... Moreover, one of the bad things in DC is that there is no
hash, so that you never knows if two files with the same name and size
are equal or different...

- b8_bavard (mldonkey)
-------------------------------------- 
Homepage: http://www.mldonkey.net/
--------------------------------------