Recently active ideas in Wuala tagged with upload

1-2 of 2 ideas
  • 1 Reply 5 Followers

    Current Task Status Last reply on May 07, 2008 12:44.

    It would be nice if in the status area (Where it shows transactions, Encrypting status, etc.) it would show what the application is doing. Like "Uploading mycooltestfile.txt (48%)" and "Maintaining mycoolmusic.mp3 (99%) - 239 Files Remaining"
    Deathbob Deathbob shared this idea on May 05, 2008 23:11. DataWraith joined Deathbob and 2 other people who like this idea. It's tagged status, upload, maintain, and files
  • 9 Replies 4 Followers

    multiple clients - temporary clients (actively push data into backupspace (other running clients of same user)) Last reply on February 28, 2008 08:44.

    hi there,

    from time to time i need to startup a wuala client at some remote destination (clients, friends, whatever...) and just log into my wuala useraccount and just dump some files/data into my wuala-space. what i am wondering about how quickly i can logout/close this temporary wuala client so that my uploaded/added data stays alive in my wuala dumpspace.

    it would be best if a running client when doing uploads, would first look for other clients running with the same credentials and then trying to dump the data first to these same-account nodes, or maybe after a while there could be also nodes of friends (wuala friends), or the nodes that a wuala node is closest to (network-wise) and so on....

    sometimes i have only little time to let this temporary wuala node running, and i dont know when i am on the safe side so that my uploaded file(s) have safely arrived inside the wuala storage space.

    maybe you are even already doing this on your clients/nodes, but it hasnt been clear, thats why i have posted this.

    i have also read about your plans, there there will be a standalone wuala java-only (non-install) client, which could (probably) run from websites (applet) and so on, without real installation on any operatingsystem that comes with java support.

    this would also make sense, to have these java (most likely) temporary clients to first try to communicate to other running clients of the same user, so that they spread modified/new data to the more stable and persistent clients of the same user first, and that those clients then take over the spreading and distribution of the data fragments/parts.

    thanks and cheers.
    nickname nickname shared this idea on February 26, 2008 15:37. nmat liked nickname's idea. It's tagged client, node, push, and multiple