š
Original date posted:2017-03-07
š Original message:> 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
Marcel Jamin [ARCHIVE] /
npub14jā¦vk3rk
2023-06-07 17:56:55
in reply to nevent1qā¦5jag
Author Public Key
npub14jegtpz2t9nfnefqqr0q4te9353e4k4x5y2528qf235ruluzsaes8vk3rkPublished at
2023-06-07 17:56:55Event JSON
{
"id": "5f4dcdcfc0cff2c207bc3e798e1e7b2d5343359db8abf7e4121a76264c32634b",
"pubkey": "acb285844a596699e52000de0aaf258d239adaa6a115451c0954683e7f828773",
"created_at": 1686160615,
"kind": 1,
"tags": [
[
"e",
"7d71aaf3aaa91e1454a25f4f9688ba685bebb747e49a8ad14b817de1aa470d06",
"",
"root"
],
[
"e",
"54f25ce01b0e512f81802a1b135747ea5ebd06550200ac0e25c28b177dfb4bd5",
"",
"reply"
],
[
"p",
"3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc"
]
],
"content": "š
Original date posted:2017-03-07\nš Original message:\u003e Why are multiple results separated by a line-feed rather than using a JSON Array?\n\u003e * Clients ought to cache historical data, and using a line-feed format allows them to simply append to a cache file.\n\u003e * 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.\n\u003e What if long descriptions require line and paragraph breaks?\n\u003e * Clients should word-wrap long lines, and JSON escapes newlines as \"\\n\" which can be used doubly (\"\\n\\n\") for paragraph breaks.\n\nI'd file this under premature optimization at the cost of\ninteroperability. If you use JSON, then please use it properly.\n\nI'd also say it's the job of the parser to offer a way of doing that,\ne.g. in .NET you can easily achieve that with Newtonsoft's JSON\nparser: http://stackoverflow.com/questions/20374083/deserialize-json-array-stream-one-item-at-a-time.\n\nOn 4 March 2017 at 09:27, Luke Dashjr via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e Investigating what it would take to add fiat currency information to Bitcoin\n\u003e Knots, I noticed Electrum currently has many implementations, one for each\n\u003e exchange rate provider, due to lack of a common format for such data.\n\u003e\n\u003e Therefore, I put together an initial draft of a BIP that could standardise\n\u003e this so wallets (or other software) and exchange rate providers can simply\n\u003e interoperate without a lot of overhead reimplementing the same thing many\n\u003e ways.\n\u003e\n\u003e One thing I am unsure about, is that currently this draft requires using XBT\n\u003e (as BTC) for Bitcoin amounts. It would seem nicer to use satoshis, but those\n\u003e don't really have a pseudo-ISO currency code to fit in nicely...\n\u003e\n\u003e Current draft here:\n\u003e https://github.com/luke-jr/bips/blob/bip-xchgrate/bip-xchgrate.mediawiki\n\u003e\n\u003e Thoughts? Anything critical missing? Ways to make the interface better?\n\u003e\n\u003e Luke\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",
"sig": "7839957de360e6b0107c82448ea8666896bbe085515b813cc1dd121c210bfc34b1af4a2aa95d8eb9fa03ac4edf918bff4b7b1c6b4c1d6c6287b35953f95374e2"
}