Hi! Given that many containers (e.g. iGoogle) only allow 10K of
persistent storage per Gadget*User, and given that 10K is not
necessarily a huge amount of space (depending on your gadget), I was
wondering if there was any proposed strategy to compress persistent data
prior to storage.

Client-side data compression is possible, of course, but there are no
standard JavaScript compression libraries that I could find, leaving the
options to:
 - write my own JavaScript implementation of DEFLATE
 - use an embedded Java applet to do DEFALTE (heavy!!)
 - ?

Server-side compression via zlib is easy enough with a custom Guice
module, but when a gadget is hosted on iGoogle/Orkut, etc. then the
server implementation is out of the control of the gadget implementer.

What's the current recommendation? "Persist less"? :-)

Are there plans to include some kind of data compression as a part of
the persistence infrastructure?

Thanks!
Dave

Reply via email to