From: Mike Hearn <mike@plan99•net>
To: Richard Moore <me@ricmoo•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Future Feature Proposal - getgist
Date: Thu, 5 Jun 2014 11:42:27 +0800 [thread overview]
Message-ID: <CANEZrP1vVY1jnV8Kdg5OWEt=Rba2PPcs3ke4tMWc6fS4wGPpOw@mail.gmail.com> (raw)
In-Reply-To: <34798C1C-FDA7-4A4C-B136-DBD4E59C254D@ricmoo.com>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
Why do you want to optimise this? getheaders is used by SPV clients not
full nodes. SPV clients like bitcoinj can and do simply ship with gist
files in them, then getheaders from the last "checkpoint" (I wish I
hadn't reused terminology like that but this is what bitcoinj calls them).
In practice when I look at performance issues with current SPV clients,
getheaders speed is not on my radar.
[-- Attachment #2: Type: text/html, Size: 461 bytes --]
next prev parent reply other threads:[~2014-06-05 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 19:30 Richard Moore
2014-06-05 3:42 ` Mike Hearn [this message]
2014-06-05 17:43 ` Richard Moore
2014-06-05 19:34 ` Pieter Wuille
2014-06-05 14:28 ` Mark Friedenbach
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='CANEZrP1vVY1jnV8Kdg5OWEt=Rba2PPcs3ke4tMWc6fS4wGPpOw@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=me@ricmoo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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