Consider alternate serialization format for client storage
Basics
Logistics
Basics
Logistics
Description
There's no urgency, but it's noticeable that the current strategy of taking JSON objects and storing them in a map structure that is itself JSON kind of sucks because it ends up escaping every quote. It would require experimentation but it may be that an XML format there would be more efficient simply due to the lack of escaping.
For local storage this doesn't matter a lot but for the cookie case it might matter a bit.
Environment
None
Activity
Scott CantorJune 8, 2020 at 11:16 PM
Merged to master.
Scott CantorApril 3, 2020 at 5:53 PM
Work is done on a dev branch. I think it's worth committing just to add pluggability, but testing on very basic real world data indicates that the XML format is only a few characters smaller, and is larger once encrypted by a non-trivial amount of 50 or so bytes, so the compression is clearly better for JSON.
It's a wash in practice, so there's no benefit to switching it.
There's no urgency, but it's noticeable that the current strategy of taking JSON objects and storing them in a map structure that is itself JSON kind of sucks because it ends up escaping every quote. It would require experimentation but it may be that an XML format there would be more efficient simply due to the lack of escaping.
For local storage this doesn't matter a lot but for the cookie case it might matter a bit.