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
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <nelsoneci@gmail.com>) id 1Wi8SU-0000m7-Ta
for bitcoin-development@lists.sourceforge.net;
Wed, 07 May 2014 20:28:54 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.175 as permitted sender)
client-ip=209.85.214.175; envelope-from=nelsoneci@gmail.com;
helo=mail-ob0-f175.google.com;
Received: from mail-ob0-f175.google.com ([209.85.214.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wi8ST-0007io-Rs
for bitcoin-development@lists.sourceforge.net;
Wed, 07 May 2014 20:28:54 +0000
Received: by mail-ob0-f175.google.com with SMTP id wo20so1878459obc.20
for <bitcoin-development@lists.sourceforge.net>;
Wed, 07 May 2014 13:28:48 -0700 (PDT)
X-Received: by 10.182.79.9 with SMTP id f9mr12029056obx.64.1399494528336; Wed,
07 May 2014 13:28:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.14.65 with HTTP; Wed, 7 May 2014 13:28:28 -0700 (PDT)
In-Reply-To: <CA+s+GJCaUX3ErgVean0e91CBorPc6RNKgYs08fOOsqNYtbd6RA@mail.gmail.com>
References: <536A8592.8010009@gmail.com>
<CA+s+GJASND3OU2e+YxUeLmSOW6pTkMwuzHCHeJnnihg6xK9Caw@mail.gmail.com>
<536A902C.6080602@gmail.com>
<CA+s+GJCaUX3ErgVean0e91CBorPc6RNKgYs08fOOsqNYtbd6RA@mail.gmail.com>
From: Nelson Castillo <nelsoneci@gmail.com>
Date: Wed, 7 May 2014 15:28:28 -0500
Message-ID: <CAPFxkVmPVp01hVMbNsseOJ=5MyCCQ9J1cYChK3-Z93UDp6qP9Q@mail.gmail.com>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b2e40163a08b404f8d536b4
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
(nelsoneci[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: 1Wi8ST-0007io-Rs
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
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, 07 May 2014 20:28:55 -0000
--047d7b2e40163a08b404f8d536b4
Content-Type: text/plain; charset=UTF-8
On Wed, May 7, 2014 at 3:18 PM, Wladimir <laanwj@gmail.com> wrote:
> On Wed, May 7, 2014 at 9:57 PM, Jameson Lopp <jameson.lopp@gmail.com>
> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I agree that it would be awesome to offer these types of stats with the
> installer; unfortunately the route I've taken has dependencies on several
> other other pieces of software to do all the heavy lifting of stats
> aggregation and chart rendering. I'm assuming that you would not want to
> build any of that processing into Bitcoin Core itself; would you be opposed
> to packaging other software along with the installer?
>
> Depends on just how much stuff it is. The idea is primarily to have an
> installer for running a (wallet-less) node as an OS background
> service.
>
> Having some statistics available would be worth some extra download
> size, otherwise it would be pretty much invisible.
>
> We'd already decided that we would need something like Python for the
> stats service. Implementing things like web services in C++ is just
> not realistic given the time constraints and the great already-written
> code that is out there. As an optional tool it should be external, not
> part of bitcoind itself.
>
> I suppose the chart rendering happens client-side? In that case the
> web service just has to collect and provide the data, and serve static
> html/js files.
>
Is SNMP an option? That way you do not need to implement clients and there
are many tools written.
> Wladimir
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b2e40163a08b404f8d536b4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, May 7, 2014 at 3:18 PM, Wladimir <span dir=3D"ltr"><<a href=3D"mailt=
o:laanwj@gmail.com" target=3D"_blank">laanwj@gmail.com</a>></span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
<div class=3D"">On Wed, May 7, 2014 at 9:57 PM, Jameson Lopp <<a href=3D=
"mailto:jameson.lopp@gmail.com">jameson.lopp@gmail.com</a>> wrote:<br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
</div><div class=3D"">> I agree that it would be awesome to offer these =
types of stats with the installer; unfortunately the route I've taken h=
as dependencies on several other other pieces of software to do all the hea=
vy lifting of stats aggregation and chart rendering. I'm assuming that =
you would not want to build any of that processing into Bitcoin Core itself=
; would you be opposed to packaging other software along with the installer=
?<br>
<br>
</div>Depends on just how much stuff it is. The idea is primarily to have a=
n<br>
installer for running a (wallet-less) node as an OS background<br>
service.<br>
<br>
Having some statistics available would be worth some extra download<br>
size, otherwise it would be pretty much invisible.<br>
<br>
We'd already decided that we would need something like Python for the<b=
r>
stats service. Implementing things like web services in C++ is just<br>
not realistic given the time constraints and the great already-written<br>
code that is out there. As an optional tool it should be external, not<br>
part of bitcoind itself.<br>
<br>
I suppose the chart rendering happens client-side? In that case the<br>
web service just has to collect and provide the data, and serve static<br>
html/js files.<br></blockquote><div><br></div><div>Is SNMP an option? That =
way you do not need to implement clients and there are many tools written.<=
/div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Wladimir<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Is your legacy SCM system holding you back? Join Perforce May 7 to find out=
:<br>
&#149; 3 signs your SCM is hindering your productivity<br>
&#149; Requirements for releasing software faster<br>
&#149; Expert tips and advice for migrating your SCM now<br>
<a href=3D"http://p.sf.net/sfu/perforce" target=3D"_blank">http://p.sf.net/=
sfu/perforce</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div></div>
--047d7b2e40163a08b404f8d536b4--
|
