Re: [leafnode-list] Will 2.x address these issues?

[Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

jom1@xxxxxxxxxx writes:

> Ozz wrote:
> > 
> > Hi Guys.
> > 
> > 
> > 1. Posting and fetching all take place sequentially.
> > News articles are posted, then retrieved.  If a local user posts a large
> > binary file then no news is fetched until posting completes.  With only
> > 256Kbps upstream, this can be a problem.  It would be useful if posting and
> > fetching were separate tasks that could run independently on the cron.
> 
> Yes, this could also be done in 1.9.x versions and this is a good idea.

I can only speak for myself, not for Cornelius who is the official
maintainer, but for my part, leafnode-1.9 will not receive any further
features. Features may or may not go into leafnode 2.0. I won't fix
small bugs in 1.9 either but rather tell people to go for 2.0beta and
fix the bug there unless it's already squished.

The only thing I can imagine as bug fix is the 1.9 file descriptor leak
fix should I receive enough information to track it down. Don't expect
any 1.9.x releases beyond 1.9.20.

> You can already run 'fetchnews' with the -P option (post only), but
> you cannot run 'fetchnews' with something like -R option (retrieve
> only).  (but not difficult to implement).

Even trivial changes will not go into 1.9.

> > 2. It does not populate itself from it's own posts.
> > If a local user posts a large binary, the post is first uploaded to my ISP's
> > server, then that same post is downloaded from my ISP's server.  This can be
> > a huge waste of time and bandwidth.  It would be useful if queued articles
> > could be streamed to the locally stored group from the queue.
> 
> You can filter your own posts :-)

Only suitable if you never post from other sites.

-- 
Matthias Andree

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."         Benjamin Franklin

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list