RE: [Mldonkey-users] directconnect strategy

[LordVyper]

Hello all

        I rounded up a list of features like you asked, its still an
"alpha" list (like mldonkey's dc support :) ), but i will improve on it
later on.
        Please note the alpha status on this, all feedback is
appreciated, and most things were based on dc++ or nmdc features. A list
of linux dc clients will follow shortly.

        If dc in mldonkey is not your game, you can skip the rest of
this email.




        Here we go:

Basic dc client:
        -connect to hub given ip:port
        -list users in hub
        -get a file list
        -download a file
        -send a file list
        -send a file

Standard dc client:
        -specify client options when connecting - link speed and name
        -limit number of slots available for upload (ie,
max_upload_slots)
        -limit number of slots for download (ie max_connections)
        -download public hub list (from "standard" location - like the
redirector)
        -filter public hub list to show only hubs containing a string
(ie, mp3, book)
        -search for a file on the hub (ie, on all users in the hub)
        -download directory (ie, all files in the directory, (and all
dirs there, recursion)
        -Favorites (hubs and users - ie, friends)
        -Add a hub to the list (based on ip:port)
        -connect from behing proxy/firewall(ie, passive - can't search
another passive or be searched by another passive)
        -Rescan shared folder to update file list on demand (with a
rescan or reshare command)
        -View hub messages - send messages to hub (public) - CHAT
        -private messages to users (send / receive) - CHAT

Advanced dc client:
        -Follow redirect (for when a hub is full and redirects you to
another one - should be optional)
        -Store file lists in files on disk, so we can open and browse
them later, instead of asking them from the user
        -limit upload slots based on current upload speed (up to a
limit) 
        -limit download slots based on current download speed (ie, open
a new slot if speed is below a certain threshold)
        -maintain unfinished downloads in a temp dir and continue them
from another client if/when available
        -http proxy when download public hub list
        -Alter shared directory
        -Automatically rescan shared folder every n minutes, or when a
new download completes
        -Add a temporary upload slot to a user 
        -Automatically give an upload slot to a friend (if upload
slot<MAX_UPLOAD_SLOTS_EVER_POSSIBLE)
        -Identify other users client brands (lcdc, mldc, dc++, etc)
        -Set an away message when messaged after a long time without
user action
        -Log messages (hub, private)
        -Handle dchub:// and dcfile:// urls (not sure about the dcfile
form)
        -Resume partial downloads.

Expert dc client:
        -Detect corruption on file (more on this later - im still
looking on to how this is done without hash - it has to do with crc 

verification ie, an extra file on a dir contains crc's for the files
there. Its only possible when a .sfv file is present)
                -Generate such crc file for our share
        -Automatically follow redirects from one hub to another
        -Maintain searches for a while - ie, If i search for a file, ask
for that file during a certain when new users arrive, to see if they 

have it.
        -Automatically search for current downloads' alternative
sources. This must be one search per 5 seconds, most hubs kick if less
than 

this, but must not be one every 5 secs, i believe there is a maximum per
minute, but i am not sure how much.1 every 15 seconds should be 

safe.
        -Multisource simultaneous download (like in mldonkey). Should
allow splitting a file in x parts (x=number of sources), getting each 

part from a different source. (this is already supported by some linux
clients)
        -Multi-hub search without having to be there (ie, search from
outside a hub - hub must allow this)
        -Block uploads to users not in hub. Close those users uploads as
soon as they leave the hub - optionnal
        -Generate html page with clickable dc links for our share, along
with current hub link



Mldonkey-specific ideas:
        -A way to use the webgui for the dc part. The tricky part should
be the file list tree-like browse in html - java script?
                -DC hub lists should go to Servers section
                -Favorite users -> friends
                -DC Queue -> vd
                -Chat part -> messages -> perphaps remake the messages
part with a java enabled chat feature?
                -Upload slots -> uploaders
                -A way to show file information in vd+num
        -The automatic asking for file lists as soon as a new user joins
the hub, so we can maintain a local hub-file-list.
        
        
As soon as the dc hub is working, I will let you know.

        Thank you all,
        Joao Correia