On Thursday, 15 April 2021 13:49:30 PDT Stottlemyer, Brett (B.S.) wrote:
> No, your description is correct. Thanks for helping to clarify.
>
> Does this help Thiago? I'm not using JSON as an input to sending a QString
> or QByteArray over the wire, I want to read a file from disk (quickly) and
On 4/15/21, 3:45 PM, "Development on behalf of Elvis Stansvik"
wrote:
With the risk of muddling things even more, but the way I understood
> Think geographic data, where I can prefetch at low-priority, and
load/process data on-demand as location changes.
was that his use case was:
Den tors 15 apr. 2021 kl 21:17 skrev Thiago Macieira
:
>
> On Thursday, 15 April 2021 07:36:08 PDT Stottlemyer, Brett (B.S.) wrote:
> > On 4/14/21, 12:53 AM, "Development on behalf of Thiago Macieira"
> >
> > wrote:
>
> > No, that was it. I assume you're caching templates which you need to
>
On Thursday, 15 April 2021 07:36:08 PDT Stottlemyer, Brett (B.S.) wrote:
> On 4/14/21, 12:53 AM, "Development on behalf of Thiago Macieira"
>
> wrote:
> No, that was it. I assume you're caching templates which you need to
> modify slightly for each reply, not plain-text JSON.
>
> Ahh, no.
Apologies if this was already sent, I meant to send yesterday and found it in a
still open window.
On 4/14/21, 12:53 AM, "Development on behalf of Thiago Macieira"
wrote:
No, that was it. I assume you're caching templates which you need to modify
slightly for each reply, not
On Tuesday, 13 April 2021 19:11:51 PDT Stottlemyer, Brett (B.S.) wrote:
> Yes, small but reparsing isn't negligible. The idea is to cache (to disk) a
> number of files, and when run, the application dynamically picks the right
> files to use. I am caching in RAM as well, once the files are
On 4/13/21, 5:23 PM, "Development on behalf of Thiago Macieira"
wrote:
Are you sure you can't just use a memory cache?
Your requirement sounds that your JSON snippet is small enough that it will
not hit the 128 MB limit any time soon but large enough that reparsing it is
not
On Tuesday, 13 April 2021 12:20:49 PDT Stottlemyer, Brett (B.S.) wrote:
> The 128 MB piece isn't an issue for my specific case, I will have smaller
> files than that. I was hoping there was an easy way to cache the REST
> response locally, where I may load the data many times before I need to
>
-project.org
Subject: Re: [Development] State of "binary JSON" in 5.15+?
On Tuesday, 13 April 2021 07:29:48 PDT Lars Knoll wrote:
The binary JSON support is deprecated and only there for backwards
compatibility. It had some issues (e.g. it couldn’t handle large JSON
files),
On Tuesday, 13 April 2021 07:29:48 PDT Lars Knoll wrote:
The binary JSON support is deprecated and only there for backwards
compatibility. It had some issues (e.g. it couldn’t handle large JSON
files), that’s why we deprecated it. It’s gone in Qt 6. I guess the docs
need some
On Tuesday, 13 April 2021 07:29:48 PDT Lars Knoll wrote:
> The binary JSON support is deprecated and only there for backwards
> compatibility. It had some issues (e.g. it couldn’t handle large JSON
> files), that’s why we deprecated it. It’s gone in Qt 6. I guess the docs
> need some adjustment
Hi Brett,
The binary JSON support is deprecated and only there for backwards
compatibility. It had some issues (e.g. it couldn’t handle large JSON files),
that’s why we deprecated it. It’s gone in Qt 6. I guess the docs need some
adjustment though.
Cheers,
Lars
On 13 Apr 2021, at 15:43,
Hi,
I was at the Contributor’s Summit where it was discussed, so I know there were
good reasons to deprecate the binary json format. The actual changes looks to
have been done in https://codereview.qt-project.org/c/qt/qtbase/+/265312.
IIUC, the original intent was that parsing the JSON
13 matches
Mail list logo
