taskmldonkey, a multi-networks file-sharing client - Tasks: task #4613, News server plugin


You are not allowed to post comments on this tracker with your current authentication level.

task #4613: News server plugin

Submitter:  Beedauchon <beedauchon>
Submitted:  Mon 05 Sep 2005 08:43:58 PM UTC
Votes: 100
Category:  Core Priority:  1 - Later
Status:  None Assigned to:  None
Open/Closed:  Open Should Start On:  Sun 04 Sep 2005 10:00:00 PM UTC
Should be Finished on:  Sun 04 Sep 2005 10:00:00 PM UTC

Sat 23 May 2009 01:37:59 AM UTC, comment #2: 

I've been suggesting this for awhile, but I guess it just occurred to me that I should actually file a task for this, and viola, it's already been done. I have to say I'm disappointed that not more people have spoken for this.

I think the actual task topic could be changed to include NZB because that's what it's really about.

spiralvoice: To check a full fledged fully dedicated project to do this, take a look at http://sabnzbd.wikidot.com/

Seems to me mldonkey would be a perfect project to integrate this functionality into too. I was looking at trying to do it myself for awhile, but was discouraged by the lack of YENC, and CRC libs for OCaml. Trying to learn OCaml and doing that type of coding at the same time seemed much.

daniel <eydaimon>
Thu 20 Apr 2006 07:15:11 PM UTC, comment #1: 

I've been looking into the option of adding nntp support by adding a
new network protocol to the FileTP module, and not use external libraries.

This seems reasonable, because nntp is a simple protocol similar to

A benefit of this aproach is that everything gets integrated with
mldonkey normal behaviour fairly easily.

A problem, though, is that nntp doesnt have support for returning the
number of bytes to be transfered, which the filetp module relies on,
because the swarmer needs to preallocate the amount and so on.
(there are some extensions to nntp for this, but they cant be relied
upon, even when they are implemented by the nntp server)

A simple solution might be to use the number of lines of the article,
which is known, and multiply it with the line-size of yenc articles,
which is also known, and add some padding. The padding can just be
discarded when it comes to decoding time.

NZB support could be added on top of this. Im not exactly sure how it
works, but it seems to just be an xml list of message id:s to be

This simple implementation ought to be enough to start with.


Joakim Verona <jave>
Group Member
Mon 05 Sep 2005 08:43:58 PM UTC, original submission:  

As discussed in RFC977


suggested features :

yenc support : http://members.tripod.com/~MikeRead/yenc.htm
nzb support : http://docs.newzbin.com/Newzbin:NZB_Specs

Alternative implementation option, write a wrapper for libnzb (which already does all that): http://nzb.sourceforge.net/?page_id=4

Beedauchon <beedauchon>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by eydaimon (Posted a comment)
  • -email is unavailable- added by eydaimon (Voted in favor of this item)

    There are 100 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-05-23 eydaimon Carbon-Copy- Added eydaimon

    Back to the top

    Powered by Savane 3.13-04b1.
    Corresponding source code