Loading Profile...
wuala commandline (linux, *nix (macosx)) improvements (history)
hi there,
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.
thanks and cheers.
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.
thanks and cheers.
6
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Get Satisfaction loves Zappos because they care about customer service.
-
Inappropriate?Hi nickname,
Yes, the cli isn't very comfortable yet. Our plans are to use http://jline.sourceforge.net/, a java command line which would give us many useful features as you know from bash and so on.
The second point (backend (core) <-> frontend (cli)) for the command line is also on our todo list. Most people use the GUI, but as cli users are often traders, this is nevertheless important for us. But I am not sure if we will be able to provide this feature until the beta release. As a cli user I hope so, but I can't promise anything.
1 person thinks
this is one of the best points
-
Inappropriate?Todays update gives you a better commandline client. As written above, I've integrated jline which enables auto completion and a command history.
I’m happy about this feature
-
Inappropriate?I think the separation between UI and worker threads is essential to successful adoption of Wuala. With a daemon working in the background, a headless 24/7 server can easily provide 99.9% uptime on Wuala storage.
The only reason I'm not yet participating in the Wuala project is that my home server is an SSH access only machine; if only I could start a Wuala daemon that runs in the background and connect to that backend from a remote front-end, there would soon be dozens of shared gigs available on a reasonably high bandwidth connection.
1 Comment Add a comment
This is one of the best points
-
of course you can easily run wuala in a screen window to manage the -nogui programm and connect from your out-door system normally with the gui version to wuala.
But at all you ́re right. The better way will be definitely a deamon. -
Inappropriate?on virtually any un*x system you could use the virtual terminal emulation tool named "screen"....
http://www.gnu.org/software/screen/
open a new screen, and create subscreens/terminals and run wualacmd (wualacommandline) there.
then simply disconnect from that screen, thus leaving the running processes alive inside that screen virtual terminal.
at any later time, you can ssh to your box, and reconnect to the disconnected screen terminal again.
this is all textmode i am talking about,
check out the screen tool if you are unfamiliar with that.
http://www.gnu.org/software/screen/
but i agree, a real server/worker and client/gui/interface separation would be even more appropriate and a good addition. -
Inappropriate?"Screen" is an option all right, but I'd categorize this option as a last resort. I'd prefer the clean version that employs a back-end daemon. This would enable the server to automatically start the service when occasionally it needs to be rebooted.
I'm actually kind of surprised the Wuala team didn't make this separation to begin with, as it's considered good practice to separate content and presentation.
EMPLOYEE
