Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » Elevate Web Builder Technical Support » Support Forums » Elevate Web Builder General » View Thread |
Messages 11 to 15 of 15 total |
Compressed and Encrypted JSON feature |
Wed, Jul 17 2013 8:52 AM | Permanent Link |
Sittro | Thank you Matthew and Raul for your answers.
I will keep testing EWB. Thank you. ---------- Note: I found a resource from the link below which study specific JSON compression algorithm. The compression ratio is interesting. Original JSON size (bytes) 1,014,099 *** Compress CJSON 47,1230 Compress HPack 99,575 Gzipped 43,550 Gzipped and Minimized 42,083 Gzipped and compressed with CJSON 37,597 Gzipped and compressed with HPack 27,358 *** http://web-resource-optimization.blogspot.com/2011/06/json-compression-algorithms.html |
Wed, Jul 17 2013 9:16 AM | Permanent Link |
Matthew Jones | Are you handling such large amounts of data? I would suggest that you need to
re-invent your UI if you do. Shipping a tenth of the data would be better than all the compression delay. /Matthew Jones/ |
Wed, Jul 17 2013 9:29 AM | Permanent Link |
Raul Team Elevate | Thanks for the link. The post does not discuss the cost of compression and decompression ? Hence it's bit unclear what the tradeoff is between additional transport latency (uncompressed json but takes longer to transmit) vs compress/decompress time (especially decompress as it's in javascript). One on their conclusions is that gzip alone is quite acceptable "as is" with no major benefit from additional compression on top. Gzip is one of the http compression algorithms so when selecting back end web server http compression would be a worthwhile thing to have : as it would also compress the app and html in addition to JSON traffic. Raul On 7/17/2013 8:52 AM, Sittro wrote: > Thank you Matthew and Raul for your answers. > I will keep testing EWB. > > Thank you. > > ---------- > Note: > I found a resource from the link below which study specific JSON compression algorithm. > The compression ratio is interesting. > > Original JSON size (bytes) 1,014,099 *** > Compress CJSON 47,1230 > Compress HPack 99,575 > Gzipped 43,550 > Gzipped and Minimized 42,083 > Gzipped and compressed with CJSON 37,597 > Gzipped and compressed with HPack 27,358 *** > > > http://web-resource-optimization.blogspot.com/2011/06/json-compression-algorithms.html > |
Thu, Jul 18 2013 12:26 AM | Permanent Link |
Sittro | Thanks you Matthew, I will try to diminish the query result.
------------- (Matthew Jones) wrote: Are you handling such large amounts of data? I would suggest that you need to re-invent your UI if you do. Shipping a tenth of the data would be better than all the compression delay. /Matthew Jones/ |
Thu, Jul 18 2013 12:27 AM | Permanent Link |
Sittro | Thank you Raul.
--------- Raul wrote: Thanks for the link. The post does not discuss the cost of compression and decompression ? Hence it's bit unclear what the tradeoff is between additional transport latency (uncompressed json but takes longer to transmit) vs compress/decompress time (especially decompress as it's in javascript). One on their conclusions is that gzip alone is quite acceptable "as is" with no major benefit from additional compression on top. Gzip is one of the http compression algorithms so when selecting back end web server http compression would be a worthwhile thing to have : as it would also compress the app and html in addition to JSON traffic. Raul On 7/17/2013 8:52 AM, Sittro wrote: > Thank you Matthew and Raul for your answers. > I will keep testing EWB. > > Thank you. > > ---------- > Note: > I found a resource from the link below which study specific JSON compression algorithm. > The compression ratio is interesting. > > Original JSON size (bytes) 1,014,099 *** > Compress CJSON 47,1230 > Compress HPack 99,575 > Gzipped 43,550 > Gzipped and Minimized 42,083 > Gzipped and compressed with CJSON 37,597 > Gzipped and compressed with HPack 27,358 *** > > > http://web-resource-optimization.blogspot.com/2011/06/json-compression-algorithms.html > |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Thursday, March 28, 2024 at 08:36 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |