-.TH "MEMCACHED_SET_SASL_CALLBACKS" "3" "January 26, 2012" "1.0.3" "libmemcached"
+.TH "MEMCACHED_SET_SASL_CALLBACKS" "3" "April 28, 2012" "1.0.7" "libmemcached"
.SH NAME
memcached_set_sasl_callbacks \- libmemcached Documentation
.
.UNINDENT
.INDENT 0.0
.TP
-.B memcached_return memcached_set_sasl_auth_data(memcached_st\fI\ *ptr\fP, const char\fI\ *username\fP, const char\fI\ *password\fP)
+.B memcached_return_t memcached_set_sasl_auth_data(memcached_st\fI\ *ptr\fP, const char\fI\ *username\fP, const char\fI\ *password\fP)
.UNINDENT
.INDENT 0.0
.TP
-.B memcached_return memcached_destroy_sasl_auth_data(memcached_st\fI\ *ptr\fP)
+.B memcached_return_t memcached_destroy_sasl_auth_data(memcached_st\fI\ *ptr\fP)
.UNINDENT
.sp
Compile and link with \-lmemcached
\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 \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
-\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.
+\fI\%memcached_get_sasl_callbacks()\fP returns the callbacks currently used by
+this memcached handle. \fI\%memcached_set_sasl_auth_data()\fP returns
+\fBMEMCACHED_SUCCESS\fP upon success.
.SH HOME
.sp
To find out more information please check: