summaryrefslogtreecommitdiff
path: root/33/3c4b8fc1fd97c2e8c45d265f525d6ba3500d35
blob: baae13d42e32c4d214d9a8c03e0122afde13981c (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
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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1WGjzs-0002R9-Km
	for bitcoin-development@lists.sourceforge.net;
	Fri, 21 Feb 2014 06:54:08 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.53 as permitted sender)
	client-ip=209.85.214.53; envelope-from=laanwj@gmail.com;
	helo=mail-bk0-f53.google.com; 
Received: from mail-bk0-f53.google.com ([209.85.214.53])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WGjzr-000834-VB
	for bitcoin-development@lists.sourceforge.net;
	Fri, 21 Feb 2014 06:54:08 +0000
Received: by mail-bk0-f53.google.com with SMTP id my13so919725bkb.26
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 20 Feb 2014 22:54:01 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.205.34.12 with SMTP id sq12mr1506257bkb.154.1392965641660;
	Thu, 20 Feb 2014 22:54:01 -0800 (PST)
Received: by 10.205.75.72 with HTTP; Thu, 20 Feb 2014 22:54:01 -0800 (PST)
In-Reply-To: <AB055C1C-76B1-4CE3-B92E-253C1C9541F6@gmail.com>
References: <CAJHLa0OD7w0Rs5ygAE4C14EWm1=x57YHG2kOee1pzxvj3FQ38g@mail.gmail.com>
	<CANEZrP2siw9hGPVsPjQ6WyohacOrs8rqs5p9ZsFY5kF0URnPWg@mail.gmail.com>
	<CA+s+GJCRqqmoHkmsq+6x9Wm6btKzdXoPjw5Af8zRDEkDE+6+zw@mail.gmail.com>
	<CA+s+GJAgs7otQB_tQNCntZ5gR+gp3+PfA+iiKPsjLu2oenaSUA@mail.gmail.com>
	<AB055C1C-76B1-4CE3-B92E-253C1C9541F6@gmail.com>
Date: Fri, 21 Feb 2014 07:54:01 +0100
Message-ID: <CA+s+GJC+1Dxa1bJ_CBQjZ6x=hb6yKbe9x3c6haQDzQvhkbYJOg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: William Yager <will.yager@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec51ba495419c1904f2e5164a
X-Spam-Score: -0.6 (/)
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
	(laanwj[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	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
X-Headers-End: 1WGjzr-000834-VB
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Bitcoin Core trial balloon:
 splitting blockchain engine and wallet
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: Fri, 21 Feb 2014 06:54:08 -0000

--bcaec51ba495419c1904f2e5164a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 21, 2014 at 7:50 AM, William Yager <will.yager@gmail.com> wrote=
:

> Running the network part of the core as a system service might make sense
> for server implementations, but it=E2=80=99s a pain in the rear for most =
users.
>

Come on, making it a possibility doesn't affect other kinds of use cases in
any way. Are you just arguing for the sake of arguing?

Wladimir

--bcaec51ba495419c1904f2e5164a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Fri, Feb 21, 2014 at 7:50 AM, William Yager <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:will.yager@gmail.com" target=3D"_blank">will.yager@gmail.com</a=
>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word">Running =
the network part of the core as a system service might make sense for serve=
r implementations, but it=E2=80=99s a pain in the rear for most users.=C2=
=A0</div>

</blockquote><div><br></div><div>Come on, making it a possibility doesn&#39=
;t affect other kinds of use cases in any way. Are you just arguing for the=
 sake of arguing?</div><div><br></div><div>Wladimir</div><div><br></div>
</div></div></div>

--bcaec51ba495419c1904f2e5164a--