On Tue, May 28, 2013 at 9:59 AM, Sven Van Caekenberghe s...@stfx.eu wrote:
And the best change is under the hood ;-)
Yes! And Pharo 1.4 running in a StackVM has been replaced by Pharo 2.0
running in a CogVM.
--
Damien Cassou
http://damiencassou.seasidehosting.st
Success is the ability to
On 28 May 2013, at 11:28, Damien Cassou damien.cas...@gmail.com wrote:
On Tue, May 28, 2013 at 9:59 AM, Sven Van Caekenberghe s...@stfx.eu wrote:
And the best change is under the hood ;-)
Yes! And Pharo 1.4 running in a StackVM has been replaced by Pharo 2.0
running in a CogVM.
That is
Ah, thanks; that is the stable/released version.
But how is the Content-Encoding:gzip done then since that was only introduced
later ?
There must be a (reverse) proxy in front of it then, but it is not visible in
the headers, just curious how things are deployed...
On 28 May 2013, at 15:03,
On 28 May 2013, at 15:39, Nicolas Petton petton.nico...@gmail.com wrote:
I'm simply using compression on the Apache side, then proxying the request to
zinc.
OK, that is clear. Thanks for the reply.
Nico
On May 28, 2013, at 3:16 PM, Sven Van Caekenberghe s...@stfx.eu wrote:
Ah,
