resume file download about xdccjs HOT 3 CLOSED

Resuming downloads means xdccJS would need some kind of database to store information about every interrupted download (botname, bot IP, package number, filename, port used).
Even worse, query the database EVERY TIME a download is started to automate the thing (to avoid using a resume() function).

I'm not sure i want to dive into that, as i'd like to keep xdccJS as light as possible. I'll think about it.

BUT !
If the idea of resuming comes from failed downloads, you could still restart it (from the beginning) like this :

// will retry indefinitely until file is downloaded
let download = () => {
  xdccJS.download('bot', '#2')
}
download()
xdccJS.on('download-err', () => {
  download()
}

from xdccjs.

In case i change my mind here's a reminder on how DCC resume works:

DCC Resume Protocol
User1 is sending the file.
User2 is receiving the file.

If User2 chooses to resume a file transfer of an existing file, the following negotiation takes place:
User2 sends:

PRIVMSG User1 :DCC RESUME filename port position

• filename = the filename sent by User1.
• port = the port number sent by User1.
• position = the current size of the file that User2 has.

User1 then responds:

PRIVMSG User2 :DCC ACCEPT filename port position

from xdccjs.

Resuming downloads means xdccJS would need some kind of database to store information about every interrupted download (botname, bot IP, package number, filename, port used).

I was totally wrong about that: if the file already exist the xdcc protocol just needs a second handshake (using DCC RESUME) specifying the file position.

from xdccjs.