-.TH "MEMCACHED_SASL_SET_AUTH_DATA" "3" "June 17, 2011" "0.49" "libmemcached"
+.TH "MEMCACHED_SASL_SET_AUTH_DATA" "3" "September 26, 2011" "0.53" "libmemcached"
.SH NAME
memcached_sasl_set_auth_data \- libmemcached Documentation
.
Please note that SASL requires the memcached binary protocol, and you have
to specify the callbacks before you connect to the server.
.sp
-memcached_set_sasl_auth_data() is a helper function defining
+\fI\%memcached_set_sasl_auth_data()\fP is a helper function defining
the basic functionality for you, but it will store the username and password
in memory. If you choose to use this method you have to call
-memcached_destroy_sasl_auth_data before calling memcached_free to avoid
-a memory leak. You should NOT call memcached_destroy_sasl_auth_data if you
-specify your own callback function with memcached_set_sasl_callbacks().
+\fI\%memcached_destroy_sasl_auth_data\fP before calling
+\fBmemcached_free\fP to avoid a memory leak. You should NOT call
+\fI\%memcached_destroy_sasl_auth_data\fP if you specify your own callback
+function with \fI\%memcached_set_sasl_callbacks()\fP.
.sp
-You as a client user have to initialize libsasl by using sasl_client_init
-before enabling it in libmemcached, and you have to shut down libsasl by
-calling sasl_done() when you are done using SASL from libmemcached.
+You as a client user have to initialize libsasl by using \fBsasl_client_init\fP before enabling it in libmemcached, and you have to shut down libsasl by
+calling \fBsasl_done()\fP when you are done using SASL from libmemcached.
.SH RETURN
.sp
-memcached_get_sasl_callbacks() returns the callbacks currently used
-by this memcached handle.
-memcached_get_sasl_set_auth_data() returns MEMCACHED_SUCCESS upon success.
+\fI\%memcached_get_sasl_callbacks()\fP returns the callbacks currently used
+by this memcached handle. \fBmemcached_get_sasl_set_auth_data()\fP returns \fBMEMCACHED_SUCCESS\fP upon success.
.SH HOME
.sp
To find out more information please check: