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
To: Wietse Venema
Cc: Postfix users
Subject: Re: memcache client for Postfix
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
-us...@postfix.org] On Behalf Of Wietse Venema
Sent: Tuesday, December 13, 2011 8:08 AM
To: Wietse Venema
Cc: Postfix users
Subject: Re: memcache client for Postfix
Combining memcache and proxymap
---
It seems that memcache is best for (surprise) doing what
...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Wietse Venema
Sent: Tuesday, December 13, 2011 8:08 AM
To: Wietse Venema
Cc: Postfix users
Subject: Re: memcache client for Postfix
Combining memcache and proxymap
---
It seems
* Wietse Venema postfix-users@postfix.org:
Wietse Venema:
Mueller, Martin (Messaging):
Thanks for all the work making memcache support available, any
thoughts on the potential use of this for anvil?
As documented, anvil blocks a client that overwhelms the server.
For that, there is
Patrick Ben Koetter:
* Wietse Venema postfix-users@postfix.org:
Wietse Venema:
Mueller, Martin (Messaging):
Thanks for all the work making memcache support available, any
thoughts on the potential use of this for anvil?
As documented, anvil blocks a client that overwhelms the
On 12/9/2011 7:57 PM, Wietse Venema wrote:
Wietse Venema:
This week I implemented a memcache client for Postfix in the hope
that it would be useful to share postscreen(8) or verify(8) caches
among multiple MTAs.
The implementation is based on libmemcache. This was not too much
work
Wietse Venema:
This week I implemented a memcache client for Postfix in the hope
that it would be useful to share postscreen(8) or verify(8) caches
among multiple MTAs.
...
Considering that memcache patches are floating around with several
problems, and the amount of time that I put
One missing word makes all the difference.
Wietse
Wietse Venema:
This week I implemented a memcache client for Postfix in the hope
that it would be useful to share postscreen(8) or verify(8) caches
among multiple MTAs.
...
Considering that memcache patches are floating around
On Sun, December 11, 2011 5:44 pm, Wietse Venema wrote:
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
Wietse Venema:
This week I implemented a memcache client for Postfix in the hope
that it would be useful to share postscreen(8) or verify(8) caches
among multiple MTAs.
The implementation is based on libmemcache. This was not too much
work, given a few examples (libmemcache is under
This week I implemented a memcache client for Postfix in the hope
that it would be useful to share postscreen(8) or verify(8) caches
among multiple MTAs.
The implementation is based on libmemcache. This was not too much
work, given a few examples (libmemcache is under-documented).
However
12 matches
Mail list logo