summaryrefslogtreecommitdiff
path: root/60/065b70d385146565fc21a1aafe43b07da5b5c3
blob: cd5c8ca13b2b92b0cd5720035ebc9d1dedd38621 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <luke@dashjr.org>) id 1QvaVe-0005hu-J5
	for bitcoin-development@lists.sourceforge.net;
	Mon, 22 Aug 2011 19:50:10 +0000
X-ACL-Warn: 
Received: from zinan.dashjr.org ([173.242.112.54])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1QvaVZ-0004ld-EZ for bitcoin-development@lists.sourceforge.net;
	Mon, 22 Aug 2011 19:50:10 +0000
Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net
	[184.4.160.40]) (Authenticated sender: luke-jr)
	by zinan.dashjr.org (Postfix) with ESMTPSA id F26875606F6;
	Mon, 22 Aug 2011 19:49:55 +0000 (UTC)
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Mon, 22 Aug 2011 15:49:36 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.4; x86_64; ; )
References: <4E52A7BA.1030208@trucoin.com>
	<CAPiTikVrw9QZAdmNwa5RCik+O4QvM4nGMZZx9Xc9L+XmtgX23w@mail.gmail.com>
In-Reply-To: <CAPiTikVrw9QZAdmNwa5RCik+O4QvM4nGMZZx9Xc9L+XmtgX23w@mail.gmail.com>
X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583
X-PGP-Key-ID: 665FC11DD53E9583
X-PGP-Keyserver: x-hkp://subkeys.pgp.net
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201108221549.44440.luke@dashjr.org>
X-Spam-Score: -0.8 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain -0.3 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QvaVZ-0004ld-EZ
Subject: Re: [Bitcoin-development] Introduction
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2011 19:50:10 -0000

On Monday, August 22, 2011 3:30:04 PM Douglas Huff wrote:
> On Aug 22, 2011 2:26 PM, "Fred Concklin" <fconcklin@trucoin.com> wrote:
> > I'm also interested in work to daemonize bitcoin on boot and furthering
> > work to bring bitcoin into general coding and implementation paradigms
> > seen on GNU/Linux platforms.
> 
> What? It already works fine in this regard using standard tools. Especially
> easy with daemontools/runit.

He said standard *coding and implementation paradigms*. This has nothing to do 
with integration with some non-standard "init replacement" that goes against 
the whole design of Unix.

What I understand this to mean, is properly abstracting the components such 
that the node, wallet, and GUI can work together while being distinct parts.
In this sense, Fred, you may be interested in working on coming up with a 
standard for a https://en.bitcoin.it/wiki/Wallet_protocol