📅 Original date posted:2017-03-13
📝 Original message:This formatting of JSON isn't unheard of though, it's typically called JSON
Streaming[1]. As long as exchanges implementing the API actually follow the
BIP and keep one JSON object per line, it shouldn't be a problem to decode.
1. https://en.wikipedia.org/wiki/JSON_Streaming
On Tue, Mar 7, 2017 at 8:07 AM Marcel Jamin via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> > Why are multiple results separated by a line-feed rather than using a
> JSON Array?
> > * Clients ought to cache historical data, and using a line-feed format
> allows them to simply append to a cache file.
> > * Parsing JSON typically requires the entire data parsed together as a
> single memory object. Using simple lines to separate results, however,
> allows parsing a single result at a time.
> > What if long descriptions require line and paragraph breaks?
> > * Clients should word-wrap long lines, and JSON escapes newlines as "\n"
> which can be used doubly ("\n\n") for paragraph breaks.
>
> I'd file this under premature optimization at the cost of
> interoperability. If you use JSON, then please use it properly.
>
> I'd also say it's the job of the parser to offer a way of doing that,
> e.g. in .NET you can easily achieve that with Newtonsoft's JSON
> parser:
> http://stackoverflow.com/questions/20374083/deserialize-json-array-stream-one-item-at-a-time
> .
>
> On 4 March 2017 at 09:27, Luke Dashjr via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
> >
> > Investigating what it would take to add fiat currency information to
> Bitcoin
> > Knots, I noticed Electrum currently has many implementations, one for
> each
> > exchange rate provider, due to lack of a common format for such data.
> >
> > Therefore, I put together an initial draft of a BIP that could
> standardise
> > this so wallets (or other software) and exchange rate providers can
> simply
> > interoperate without a lot of overhead reimplementing the same thing many
> > ways.
> >
> > One thing I am unsure about, is that currently this draft requires using
> XBT
> > (as BTC) for Bitcoin amounts. It would seem nicer to use satoshis, but
> those
> > don't really have a pseudo-ISO currency code to fit in nicely...
> >
> > Current draft here:
> >
> https://github.com/luke-jr/bips/blob/bip-xchgrate/bip-xchgrate.mediawiki
> >
> > Thoughts? Anything critical missing? Ways to make the interface better?
> >
> > Luke
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170313/b8f95ee6/attachment.html>;
Andrew LeCody [ARCHIVE] /
npub10q…rt9pg
2023-06-07 17:56:55
in reply to nevent1q…tann
Author Public Key
npub10qzuhfx33295fwj8eq86vlfc9e5mkzj5lzzpcwhj2yqyae3jetysxrt9pgPublished at
2023-06-07 17:56:55Event JSON
{
"id": "9c39317a44ef9e93b81ab0165513ed0abcf0374af6796544afdbb84d0822c358",
"pubkey": "7805cba4d18a8b44ba47c80fa67d382e69bb0a54f8841c3af251004ee632cac9",
"created_at": 1686160615,
"kind": 1,
"tags": [
[
"e",
"7d71aaf3aaa91e1454a25f4f9688ba685bebb747e49a8ad14b817de1aa470d06",
"",
"root"
],
[
"e",
"5f4dcdcfc0cff2c207bc3e798e1e7b2d5343359db8abf7e4121a76264c32634b",
"",
"reply"
],
[
"p",
"acb285844a596699e52000de0aaf258d239adaa6a115451c0954683e7f828773"
]
],
"content": "📅 Original date posted:2017-03-13\n📝 Original message:This formatting of JSON isn't unheard of though, it's typically called JSON\nStreaming[1]. As long as exchanges implementing the API actually follow the\nBIP and keep one JSON object per line, it shouldn't be a problem to decode.\n\n1. https://en.wikipedia.org/wiki/JSON_Streaming\n\nOn Tue, Mar 7, 2017 at 8:07 AM Marcel Jamin via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e \u003e Why are multiple results separated by a line-feed rather than using a\n\u003e JSON Array?\n\u003e \u003e * Clients ought to cache historical data, and using a line-feed format\n\u003e allows them to simply append to a cache file.\n\u003e \u003e * Parsing JSON typically requires the entire data parsed together as a\n\u003e single memory object. Using simple lines to separate results, however,\n\u003e allows parsing a single result at a time.\n\u003e \u003e What if long descriptions require line and paragraph breaks?\n\u003e \u003e * Clients should word-wrap long lines, and JSON escapes newlines as \"\\n\"\n\u003e which can be used doubly (\"\\n\\n\") for paragraph breaks.\n\u003e\n\u003e I'd file this under premature optimization at the cost of\n\u003e interoperability. If you use JSON, then please use it properly.\n\u003e\n\u003e I'd also say it's the job of the parser to offer a way of doing that,\n\u003e e.g. in .NET you can easily achieve that with Newtonsoft's JSON\n\u003e parser:\n\u003e http://stackoverflow.com/questions/20374083/deserialize-json-array-stream-one-item-at-a-time\n\u003e .\n\u003e\n\u003e On 4 March 2017 at 09:27, Luke Dashjr via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\n\u003e \u003e Investigating what it would take to add fiat currency information to\n\u003e Bitcoin\n\u003e \u003e Knots, I noticed Electrum currently has many implementations, one for\n\u003e each\n\u003e \u003e exchange rate provider, due to lack of a common format for such data.\n\u003e \u003e\n\u003e \u003e Therefore, I put together an initial draft of a BIP that could\n\u003e standardise\n\u003e \u003e this so wallets (or other software) and exchange rate providers can\n\u003e simply\n\u003e \u003e interoperate without a lot of overhead reimplementing the same thing many\n\u003e \u003e ways.\n\u003e \u003e\n\u003e \u003e One thing I am unsure about, is that currently this draft requires using\n\u003e XBT\n\u003e \u003e (as BTC) for Bitcoin amounts. It would seem nicer to use satoshis, but\n\u003e those\n\u003e \u003e don't really have a pseudo-ISO currency code to fit in nicely...\n\u003e \u003e\n\u003e \u003e Current draft here:\n\u003e \u003e\n\u003e https://github.com/luke-jr/bips/blob/bip-xchgrate/bip-xchgrate.mediawiki\n\u003e \u003e\n\u003e \u003e Thoughts? Anything critical missing? Ways to make the interface better?\n\u003e \u003e\n\u003e \u003e Luke\n\u003e \u003e _______________________________________________\n\u003e \u003e bitcoin-dev mailing list\n\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170313/b8f95ee6/attachment.html\u003e",
"sig": "fc9b43461df269da8d532bccdfb33026523b0f89025141f963f4d6d769eeaa415b9a44d0e4c98347904a74560180fa61b9d30f5b169234b1ce4fa96699ce869c"
}