From: Tim Ruffing <tim.ruffing@mmci.uni-saarland.de>
To: Tim Ruffing <tim.ruffing@mmci.uni-saarland.de>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Currency/exchange rate information API
Date: Mon, 06 Mar 2017 17:02:53 -0500 [thread overview]
Message-ID: <1488837773.2134.3.camel@mmci.uni-saarland.de> (raw)
In-Reply-To: <1488837256.2134.1.camel@mmci.uni-saarland.de>
On Mon, 2017-03-06 at 16:54 -0500, Tim Ruffing via bitcoin-dev wrote:
>
> > Pushing is what longpolling does.
> >
>
> That makes a lot of sense, yes.
>
Forgot one thing:
For longpolling, maybe we would like to have the possibility to request
some periodic message from the server. Otherwise clients cannot
distinguish between the situations 1. "value is still in the requested
bounds (minrate, maxrate)" and 2. "connection has dropped". So the user
may take a wrong decision because he assumed that the value is still
in bounds holds but actually the server has died.
Tim
next prev parent reply other threads:[~2017-03-06 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 8:27 [bitcoin-dev] Currency/exchange rate information API Luke Dashjr
2017-03-04 15:18 ` アルム カールヨハン
2017-03-06 5:37 ` Tim Ruffing
2017-03-06 7:09 ` Luke Dashjr
2017-03-06 8:14 ` Jonas Schnelli
2017-03-06 21:54 ` Tim Ruffing
2017-03-06 22:02 ` Tim Ruffing [this message]
2017-03-06 22:21 ` Luke Dashjr
2017-03-06 22:14 ` Luke Dashjr
2017-03-06 22:30 ` Tim Ruffing
2017-03-06 22:38 ` Tim Ruffing
2017-03-06 23:14 ` Andreas Schildbach
2017-03-07 9:29 ` Marcel Jamin
2017-03-13 18:10 ` Andrew LeCody
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=1488837773.2134.3.camel@mmci.uni-saarland.de \
--to=tim.ruffing@mmci.uni-saarland.de \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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