Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMI<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=867.msg10228#msg10228">Quote from: lfm on August 19, 2010, 10:28:19 AM</a></div><div class="quote">So what do you mean the gui and the daemon should be separated? They already are. You can build the separate daemon. Do you need a separate build of only the gui? I can't see why.<br/></div><br/>Bitcoin is a P2P network, so the program should be running all the time. However, I don't need to be looking at a GUI all that time, so it makes sense to have a daemon. Currently, you have to stop the daemon when you want to start the GUI version, which breaks the network for a moment.<br/><br/>Some P2P applications like aMule do this properly. The daemon is running all the time, and when you want to interact with it, you start the separate GUI, which connects to the daemon. Most importantly, the GUI can run on a different machine from the daemon.<br/><br/>Such a setup would be great for mobile Bitcoin usage. You run the daemon on your "server" machine, and you connect to it with a GUI on your mobile device. I think this has been already discussed in a different context, but the same mechanism applies.<br/><br/>However, you can already use the JSON-RPC mechanism to build a separate GUI, so there is no immediate need to change the mainline client. </div> text/html