linuxdcpp-team team mailing list archive

[Steven Sheehy <steven.sheehy@xxxxxxxxx>]

Looks like you filed two bugs for the same thing accidentally.



On Sep 17, 2010, at 8:24 AM, Razzloss <razzloss@xxxxxxxxx> wrote:

> Public bug reported:
> 
> Seems that the lists are still grouped by file. This grouping makes some
> sense with the downloads, but not with uploads. The rare occurance where
> user downloads a file with same name can probably be fixed by removing
> the findFile-call for downloads (since as far as I can tell it's
> redundant anyway and only leads to incorrect behavior described
> previously. Removing the call of course fixes this only if the core does
> something sensible and doesn't clump the download together with the
> previous one.).
> 
> But for uploads I really think the grouping should be by user and file.
> So that each user downloading file would be added to the list separately
> and not like now that all the users are clumped to one single row. With
> segmented downloading file/user row would be updated when segment
> completes. If this is at all possible with current core without extreme
> performace penalties, is a another question.
> 
> ** Affects: linuxdcpp
>     Importance: Undecided
>         Status: New
> 
> -- 
> Finished transfers still grouped by file
> https://bugs.launchpad.net/bugs/641305
> You received this bug notification because you are a member of LinuxDC++
> Team, which is subscribed to LinuxDC++.
> 
> Status in Linux DC++: New
> 
> Bug description:
> Seems that the lists are still grouped by file. This grouping makes some sense with the downloads, but not with uploads. The rare occurance where user downloads a file with same name can probably be fixed by removing the findFile-call for downloads (since as far as I can tell it's redundant anyway and only leads to incorrect behavior described previously. Removing the call of course fixes this only if the core does something sensible and doesn't clump the download together with the previous one.).
> 
> But for uploads I really think the grouping should be by user and file. So that each user downloading file would be added to the list separately and not like now that all the users are clumped to one single row. With segmented downloading file/user row would be updated when segment completes. If this is at all possible with current core without extreme performace penalties, is a another question.
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~linuxdcpp-team
> Post to     : linuxdcpp-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~linuxdcpp-team
> More help   : https://help.launchpad.net/ListHelp