[AWS] Preferred method for pre-compressing static content

[Patrice]

>From my experience, for intensive usage of the web site, 
depending also on the audience, but using proper HTTP Cache pragma save
a lot in terms of connections

i just recompiled my imgsvr project using the latest AWS / GNAT GPL tool
chain, but i hav'nt make a deep dive yet of the "standard" AWS
support/usage of thoses pragmas.

I profit this message to also thank's the gnatcore team for the very
good job made on gprbuild system that saves my a lots of time in
compiling cross language and library (dynamic / static) support.

happy new year every one.

Patrice

Le dimanche 09 janvier 2011 à 13:19 +0100, Thomas Løcke a écrit :
> Hey,
> 
> I've got a bunch of static content (CSS, JS, XML and similar) that I'd
> like to pre-compress, but I can't quite decide on how to best go about
> this.
> 
> My current solution make use of Ada.Streams.Stream_IO and ZLib. I
> simply create a .gz version of the original static content, if the
> size of the original file is bigger than 400 bytes and its content is
> text, but I'm not sure if this is the best way to go about it.
> 
> Anybody got any experiences they'd like to share?
> 
> :o)
> Thomas Løcke
> _______________________________________________
> AWS mailing list
> AWS at lists.adacore.com
> /no-more-mailman.html