BitShares Forum
Main => Technical Support => Topic started by: cn-members on December 09, 2014, 08:12:16 am
-
Current Situation
I’m using bitshares wallet in both linux and windows. While the GUI wallet is very intuitive for most users including me, the command line version is definitely more stable and less resource intensive, and thus more suitable to be left open for days.
Therefore, my best strategy is opening bitshares_client in server mode + web_wallet. However, I found that it is just too complex to tell others to do so, and the ‘http_start_server’ command is not enough to do the magic.
Suggestions
If I can have two commands:
1. http_start_server, which will runs everything you need to have a web_wallet in your own browser
2. http_stop_server, which can close the web_wallet interface when I don’t need it, and thus leave the command line wallet open to make everything stay in sync.
In brief, I'm suggesting the following startegy:
1. run the core of BTS wallet as a service in the background to make everything stay in sync with the lowest resource consumption
2. opens up the shell, whether command line or GUI, for user interface only when it is needed.
-
+5%
-
Already supported.
-
If you run a delegate you need to enable the server because the feed programs access the RPC via the HTTP web server... so for people who need RPC they are outta luck unless we switch to using the other RPC port.. which seems noone is doing (no documentation that I can find).
-
Documentation for feed scripts suck currently .. though there is a page for them in the wiki