Hello, I could find the following entry in the FAQ.
http://code.google.com/p/memcached/wiki/FAQ | * How does memcached's authentication mechanisms work? | | It doesn't! Memcached is the soft, doughy underbelly of your application. | Part of what makes the clients and server lightweight is the complete lack | of authentication. New connections are fast, and server configuration is | nonexistent. But the development roadmap says as follows: http://code.google.com/p/memcached/wiki/DevelopmentRoadmap | * Development Branch: 1.5 | - protocol extension support | think mod_auth for type of mechanism to add to core | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Amazing! Is these any design proposals? Or, could you introduce me who is working on this efforts? I've worked on development of secure web application platform using SELinux for a few years. Nowadays, memcached becomes a significant facility for various kind of web applications, so we cannot ignore access controls on the key-value store shared by multiple web applications. So, I'm interested in the description on the roadmap, and looking for more detailed information about this project. Thanks, -- OSS Platform Development Division, NEC KaiGai Kohei <[email protected]>
