From: Nelson Castillo <nelsoneci@gmail.com>
To: Wladimir <laanwj@gmail.com>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
Date: Wed, 7 May 2014 15:28:28 -0500 [thread overview]
Message-ID: <CAPFxkVmPVp01hVMbNsseOJ=5MyCCQ9J1cYChK3-Z93UDp6qP9Q@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJCaUX3ErgVean0e91CBorPc6RNKgYs08fOOsqNYtbd6RA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 3065 bytes --]
next prev parent reply other threads:[~2014-05-07 20:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 19:12 [Bitcoin-development] Announcing the Statoshi fork Jameson Lopp
2014-05-07 19:46 ` Wladimir
2014-05-07 19:57 ` Jameson Lopp
2014-05-07 20:18 ` Wladimir
2014-05-07 20:25 ` Mike Hearn
2014-05-07 20:31 ` Charlie 'Charles' Shrem
2014-05-07 21:07 ` Wladimir
2014-05-08 0:47 ` Gregory Maxwell
2014-05-08 7:45 ` Wladimir
2014-05-08 10:08 ` Mike Hearn
2014-05-08 10:32 ` Wladimir
2014-05-07 20:28 ` Nelson Castillo [this message]
2014-05-08 11:22 ` Wladimir
2014-05-07 20:35 ` Jameson Lopp
2014-05-07 21:04 ` Charlie 'Charles' Shrem
2014-05-07 19:50 ` Mike Hearn
2014-05-07 20:00 ` Jameson Lopp
2014-05-07 20:12 ` Mike Hearn
2014-05-07 19:55 ` Pavol Rusnak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPFxkVmPVp01hVMbNsseOJ=5MyCCQ9J1cYChK3-Z93UDp6qP9Q@mail.gmail.com' \
--to=nelsoneci@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=laanwj@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox