> Combining memcache and proxymap
> -------------------------------
>
> It seems that memcache is best for (surprise) doing what it was
> designed for: a cache layer on top of a persistent database, where
> the cache is maintained by the clients of the persistent database.
Completed in snapshot 20111213:
Support for a persistent backup database in the memcache client.
The memcache client updates the memcache whenever it looks up or
modifies information in the persistent database.
The persistent database can be shared with the proxymap service,
provided that it is listed as "proxy:maptype:mapname" in the
proxy_read_maps or proxy_write_maps parameter value (depending on
whether the access is read-only or read-write).
Support for proxymap-over-tcp (proxy:maptype:mapname@host:port) is
under development. This would support postscreen/verify cache
sharing, with or without memcache (memcache would help to avoid a
performance bottleneck).
Elimination of dependencies on the libmemcache library. Postfix
memcache support is now compiled in by default.
Wietse
