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
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1Qr5Cv-0005KV-6F
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Aug 2011 09:36:13 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.175 as permitted sender)
client-ip=209.85.160.175; envelope-from=witchspace81@gmail.com;
helo=mail-gy0-f175.google.com;
Received: from mail-gy0-f175.google.com ([209.85.160.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Qr5Ct-00008Z-1o
for bitcoin-development@lists.sourceforge.net;
Wed, 10 Aug 2011 09:36:13 +0000
Received: by gyg4 with SMTP id 4so686276gyg.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 10 Aug 2011 02:36:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.214.9 with SMTP id m9mr7898908ybg.345.1312968965655; Wed,
10 Aug 2011 02:36:05 -0700 (PDT)
Received: by 10.150.52.5 with HTTP; Wed, 10 Aug 2011 02:36:05 -0700 (PDT)
Date: Wed, 10 Aug 2011 09:36:05 +0000
Message-ID: <CAJNQ0sudgAnr9hMUMt8grSNTYswunyNnp25Uzw5t17ucxTBoGA@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=000e0cd378dccc8c1e04aa236845
X-Spam-Score: 0.9 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(witchspace81[at]gmail.com)
1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?209.85.160.175>]
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
1.5 SF_NO_SPF_SPAM SF_NO_SPF_SPAM
-1.4 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Qr5Ct-00008Z-1o
Subject: [Bitcoin-development] Change to multiple executables?
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: Wed, 10 Aug 2011 09:36:13 -0000
--000e0cd378dccc8c1e04aa236845
Content-Type: text/plain; charset=ISO-8859-1
All,
In the current mainline client everything is lugged into one executable
(with an optional daemon-only one). I think this is a bad idea for various
reasons, and would propose something like:
- bitcoind: bitcoin daemon
- bitcoin(-qt): bitcoin GUI executable
- bitcoincl: bitcoin RPC command line
By default, all three would be built. In non-GUI mode, only bitcoind and
bitcoincl are built (the names are obviously open for discussion).
Advantages:
- It is more clear to the user. One command, one function.
- It simplifies the main functions.
- The UI would no longer double-function as daemon. It is a waste of
memory to link the UI libs if you only want to run a background process.
- The UI and daemon would no longer double-function as RPC call. Why load
the code for UI and network if you just want to send a single command over
JSONRPC? This would also prevent accidentally launching the daemon/UI
locally if you just want to send a command and forget to give an argument.
JS
--000e0cd378dccc8c1e04aa236845
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
All,<br><br>In the current mainline client everything is lugged into one ex=
ecutable (with an optional daemon-only one). I think this is a bad idea for=
various reasons, and would propose something like:<br><ul><li>bitcoind: bi=
tcoin daemon</li>
<li>bitcoin(-qt): bitcoin GUI executable</li><li>bitcoincl: bitcoin RPC com=
mand line<br></li></ul>By default, all three would be built. In non-GUI mod=
e, only bitcoind and bitcoincl are built (the names are obviously open for =
discussion). <br>
<br>Advantages:<br><ul><li>It is more clear to the user. One command, one f=
unction.</li><li>It simplifies the main functions.</li><li>The UI would no =
longer double-function as daemon. It is a waste of memory to link the UI li=
bs if you only want to run a background process.</li>
<li>The UI and daemon would no longer double-function as RPC call. Why load=
the code for UI and network if you just want to send a single command over=
JSONRPC?=A0 This would also prevent accidentally launching the daemon/UI l=
ocally if you just want to send a command and forget to give an argument.</=
li>
</ul><span class=3D"Apple-style-span" style=3D"color: rgb(0, 0, 0); font-fa=
mily: verdana,sans-serif; font-size: 13px; font-style: normal; font-variant=
: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; o=
rphans: 2; text-indent: 0px; text-transform: none; white-space: normal; wid=
ows: 2; word-spacing: 0px; background-color: rgb(236, 237, 243);"></span>JS=
<br>
--000e0cd378dccc8c1e04aa236845--
|
