Gibt es einen bestimmten Grund, dass im Mac-Client (und nach hösagen auch im WinClient) maximal 100GB Festplattenplatz füla zur Verfügestellt werden kön?
Im Linux-Client scheint es die Begrenzung nicht zu geben..
would be great if the wuala commandline would be more comfortable like command-completion, command-history and all these little features that come with todays normal commandline shells like bash, and so on....
also, maybe its possible to create a wuala core (worker) thread/process to which the wuala commandline client (control interface) could connect. therefore the restart on update and all this stuff would be much easier.
i think the amule project works similar to that, that they created a worker daemon and the commandline control utility simply transfers commands/statusmessages and queries the actual working core/daemon.
there is also an amule webinterface wich is only a frontend to the actual working daemon in the background.
this way there could be several frontends like the current gui stuff on varying os systems and the backend being universal. all this could be realized in java i guess and could be less platform dependant during development and so on.
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.