DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=date:from:to:cc:subject:message-id:mime-version:content-type:content-disposition:user-agent;
        b=NzRitj7+GsF4cKlCWSJfECOarNRRFnBbD7mUsGpVSLDq8906pp5GNprNDP/m76i8e5M+py6sY6bpDZHwHo9CAYEnE7pCCOjvYR56JjPkQXPJFdRVkR2yMoTHkAH/Yv8tdC8uC2sSThliMpCvgBbnQniBkDxohVT7ax8j/kaxArY=
Date: Fri, 1 Feb 2008 17:21:02 +0300
From: Tomash Brechko <tomash.brechko@gmail.com>
To: talk@openhack.ru
Cc: memcached@lists.danga.com
Subject: [ANN] memcached-patched & memcached_gzip
Message-ID: <20080201142102.GF4822@moonlight.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i

Hello,

This message is to make two announcements.

http://openhack.ru/memcached-patched has been populated finally.  For
now, the only things you will find there are Git daily mirror of
memcached svn repo, and the implementation of noreply mode, to be used
together with Cache::Memcached::Fast (and other clients that are
willing to support it).  There are also some extensions to
Cache::Memcached, but they are obsoleted by Cache::Memcached::Fast.

Also, today we released the extension for nginx (popular reverse HTTP
proxy, see the previous announce,

  http://list.openhack.ru/Lists/talk/Message/4.html

) to serve _compressed_ data directly from memcached, with automatic
decompression for clients that can't handle compressed data (older
browsers, some indexing bots).  With this, you can have most part of
your static content in RAM right on the nginx balancing host that
interacts with the outside world, to be served instantly.  See

  http://openhack.ru/nginx-patched/wiki/MemcachedGzip

for details.


-- 
   Tomash Brechko