Hello jD team and community!

On my way to work i suddenly got an idea. In times of cloud networking, browseraddons which make you have your profile whereever you are and other centralizing stuff, it would be great to have an option for jDownloader to save a linklist on a remote server, so i can access my current downloads on several computers (e.g. at home, where i live during week, whereever).

How could this look like:

• user goes to Settings -> Download & Connections
• another area, maybe under "Download Control" with a TextInput is visible. Maybe named "Remote Linklist"
• User enters a link to a file on a server. Could probably be the same sort of file which is created when making a linklist backup
• maybe a Checkbox item stating "Priorize Remote Linklist over local downloads"

The last listitem is just an idea. It could arrange that jDownloader first looks on the server for the file and if the file is found, it compares the state of the links with the local ones (preventing that links are double-, triple- and multiple-added) and if the list contains new/not-yet-downloaded links, it adds them to the local download list.

Another idea complementing this could be another TextInput combined with a Checkbox "autocreate remote backup" (Checkbox) and "time interval to upload the linklist to the server", but i don't know if this goes to far as this provides an implementation of some sort of write access to the server (FTP or something similar) which would be some additional overhead to add this function.
But being more simple, i think for the first, an option just to add an url to a linklist file manually would be very great. It's not that big of a problem to manually upload a file to a server. But i guess, in the Java world there's plenty of libs which make such things possible, ain't it?

Maybe i'll have a look myself at how one could start implementing it. Is there some space for additional developers in the jDownloader team? I won't make promises for now and Java is not my native programming language, but it would be something good to do in my spare time, as i think i actually have way too less dev-related hobby projects for someone working in a closely related branch.


So, what do you think, dear community? Is this idea realizeable or did i overlook something which makes it kind of impossible?

Best regards,
ayb.

[raztoki]

I'd say mission impossible in the current implementation. The only way I could see you doing this would be to simple addon or even external program via simple text list of links. Maybe over ftp (with ssl?) with read and write. Your addon logins to ftp > grabs list > copies the top 10 links in the file, then removes them > uploads the new file back to the server, then disconnects. Assuming your clients can not logging in at the same time, ftp max logins == 1.

From the perspective of the team we wont be doing this, so ill mark it as declined. If your capable of making this yourself it be the only way its going to happen.

Okay. As i said: it was just an idea

Is the "mission impossible" thingy because of the architecture jDownloader is built? The additional idea with the ftp upload... okay, that was just a possible extension of the idea itself, but starting a http connection to a manually uploaded file and parsing its content (the linklist) - is this really that hard?

I mean, jDownloader does a lot of http connections to parse content, i guess.
Don't get this wrong, i don't want to try and persuade you in any way; just want to understand.
Or does this simply not fit into jD's concept, the way it works/should work?

Best regards,
ayb.

[raztoki]

The config system was just rewritten, to share a common db or even remote config system would require another rewrite, along with all the other implications with jd controllers. This idea while great, just wouldn't get used enough to justify another rewrite. Your better off writing it as addon or external program as explained in my answer. JD is designed more at the single user level and even down to the computer even though its portable. Links are added into queue (save paths) based on the computer that imports (default path\package customiser) and its storage medium mappings (windows a-z, unix/linux /wherever).

To be honest I never read your complete post (bottom of the bullet points), then scanned the rest. I now see we had similar ideas. My answer is how I would approach it if I was coding it, a very simple addon or external tool either way can integrate with JD easily enough (export into clipboard or API). If it was external you could also use the same process for other downloading programs if you where ever to switch.

Best of luck in your endeavours.

Hey,

thanks for your answer

Originally Posted by raztoki

The config system was just rewritten, to share a common db or even remote config system would require another rewrite, along with all the other implications with jd controllers. This idea while great, just wouldn't get used enough to justify another rewrite.

Yeah, that sounds reasonable.

To be honest I never read your complete post (bottom of the bullet points), then scanned the rest. I now see we had similar ideas.

Hehe. I slightly thought so... i know that, when there's not much time allowing only a quick-scan of whatever text. Just happens that some details get lost. No problem.

My answer is how I would approach it if I was coding it, a very simple addon or external tool either way can integrate with JD easily enough (export into clipboard or API). If it was external you could also use the same process for other downloading programs if you where ever to switch.

Sounds great. When reading your first answer, i also thought about whether the clipboard thingy could be an applicable approach. I'll have a look at the API as well; i guess this weekend i'll have some time.

Best of luck in your endeavours.

:thumbup: Thank you!

Why don't you use a cloud syncing service for jD's config folder?

The only measures you need to take are that your cloud folder is synced

1) cloud -> desktop before you start jD;

2) desktop -> cloud before you leave/shutdown your computer.

Just use existing infrastructure/components.

[raztoki]

because JD isn't designed to share same configs. You do that you end up many controller issues.

That's implied by the "shutdown your computer", but I could have written that more explicitly.

I didn't read that it was allyourbase's intention to run several jD's with the same config simultaneously.