public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related services
Date: Fri, 8 Aug 2014 11:45:19 +0200	[thread overview]
Message-ID: <CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 245 bytes --]

Given that we're not running out of service bits and service bits mean you
don't have to try connecting to every node to find out what services it
supports, why not keep using the existing extension mechanism until we
start running out of bits?

[-- Attachment #2: Type: text/html, Size: 275 bytes --]

  reply	other threads:[~2014-08-08  9:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  3:38 [Bitcoin-development] NODE_EXT_SERVICES and advertising related services Jeff Garzik
2014-08-08  9:45 ` Mike Hearn [this message]
2014-08-08  9:56   ` Wladimir
2014-08-08 10:01     ` Mike Hearn
2014-08-08 10:15       ` Wladimir
2014-08-08 10:26         ` Wladimir
2014-08-08 10:41           ` Christian Decker
2014-08-08 11:22             ` Jeff Garzik
2014-08-08 11:33       ` Jeff Garzik
2014-08-08 11:38         ` Mike Hearn
2014-08-08 11:59           ` Wladimir
2014-08-08 12:06             ` Jeff Garzik
2014-08-08 12:11             ` Jeff Garzik
2014-08-08 12:15               ` Wladimir
2014-08-08 12:11             ` Mike Hearn
2014-08-08 12:15               ` Jeff Garzik
2014-08-08 12:16               ` Wladimir
2014-08-08 12:34               ` Wladimir
2014-08-08 13:55                 ` Mike Hearn
2014-08-08 12:04           ` Jeff Garzik
2014-08-08 12:13             ` Mike Hearn

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='CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com' \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@bitpay.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