On Tue, Jun 24, 2014 at 6:40 PM, Jorge Timón <jti...@monetize.io> wrote: > > I think he means that the wallet shouldn't be running as much as it is > currently doing. > But yes, I think you're right about wallets and GUIs not necessarily > mapping 1:1.
I haven't been talking about the GUI at all in this entire conversation. When I say wallet, I mean the wallet code. There are very few reasons for running a wallet 24/7. One could be if you're running an exchange that has to send and receive transactions all the time. But that's an exception - in the usual merchant/end-user case you're mostly receiving transactions and sometimes manually or batched- sending them. No need to leave the wallet running, exposed to the network outside those times. How the wallet GUI (if any) relates to the wallet code is a completely different topic, and a much less pressing matter. Anything from 'GUI uses wallet as a library' (multibit, electrum, bitcoin core) to elaborate client-server protocols (btcd, coinvault?) are acceptable depending on the use case. Wladimir ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
