#1
|
|||
|
|||
Feature request: new priority level "Last Resort"
Hi,
I often add packages with links from multiple hosters (mirrors). I have a premium account on ShareOnline, and the other hoster that occurs in this package is UploadedTo. Let's also assume I have set the "maximum of simultaneous downloads per host" to 10 in the JD2 settings, but the package has more than 10 files. And I have an account on 9kw.eu and some credits left. Currently, I need to disable all UploadedTo links, otherwise JD2 will start the first 10 downloads on ShareOnline and the 11th on UploadedTo. ShareOnline will then be used for the 12th and subsequent files. Because UploadedTo is by far the slowest hoster for free users, the 11th file will finish a long time after all the others from the package. So, the package takes as long as file #11 takes on the slow hoster. And it unnecessarily consumes my credits on 9kw. On the other hand, I would like to keep the UploadedTo links enabled just in case one (or more) of the files can not be downloaded from ShareOnline at the moment because one of the often occurring temporary hoster problems on ShareOnline. So I have to choose between - disabling UploadedTo but needing to check the state from time to time - keep UploadedTo enabled, but take longer than needed and consuming credits This is where my idea comes into play: Keep the UploadedTo links enabled and set them to "Last Resort" priority. The ShareOnline Links would have any other (means: higher) prority. Even "Low" is higher than "Last Resort". "Last Resort" priority means: Don't start this link unless the file is not downloadable on any of the mirrors with higher priority because of e.g. "host problem", "file not found", "no free user slots available", "try again later" ... "no free user slots available" is for users without ShareOnline premium account. "try again later" is a typical situation on Oboom. It would also be helpful to have a new condition "Hoster" in the packagizer, so I can automatically set all added UploadedTo links to "Last Resort" priority. What do you think about this ? Thanks and Regards, Ubuntix |
#2
|
||||
|
||||
Not necessary in my opinion.
Your case is far too complex. You want JD to usually avoid the free mode completely but download in free mode in case everything else fails (the chance of this is low too). There are so many possibilities to solve this: -Disable the uploaded links -Disable free mode for uploaded -Disable captchas -Skip the uploaded links (And yes, if you do any of these, the mirror handling will not use these links in case the shareOnline mirror fails) GreeZ psp
__________________
JD Supporter, Plugin Dev. & Community Manager
Erste Schritte & Tutorials || JDownloader 2 Setup Download |
#3
|
||||
|
||||
I think it would make more sense to use a special marker than priority. Because with your idea you no longer can use different hosts as "last resort" mirrors because you dont have any way to give ul higher priority than other mirror. A special mark (lets call it "mirror link") will do as you have it in mind but you still can use priorities to use different hosts as fallback. What do you say about this?
__________________
JD-Dev & Server-Admin |
#4
|
|||
|
|||
@pspzockerscene
I would not use "free mode" or "captcha" as criterion. It might as well happen that I add a package with Zippyshare, Oboom, and UplaodedTo. So, no premium hoster in the package, but still UplaodedTo is by far the slowest, worth to be avoided if somehow possible. And in this case, I would even set the Oboom links to be avoided if possible, because Zippyshare is nearly as fast as a premium account, only witth no simultaneoous downloads. And I'm also thinking about the users who don't have any free account at all. Even then, UplaodedTo is the slowest, and it has another disadvantage: If used more than 2 times per 3 hours, it takes 2 captchas per download, consuming more credits. @Jiaz Yes, you are right. A special marker would be better. In my use case with Zippyshare, Oboom and UplaodedTo, there should be a higher priority for Oboom than for UplaodedTo. But independently of the question "set marker" or "disable", it would be helpful to have a "Hoster" criterion in the packagizer. |
#5
|
||||
|
||||
Set Marker will then be available via action/context menu and of course via packagizer
__________________
JD-Dev & Server-Admin |
#6
|
|||
|
|||
Cool , thanx
|
#7
|
||||
|
||||
Thank me when its done;)
__________________
JD-Dev & Server-Admin |
Thread Tools | |
Display Modes | |
|
|