no, that alone brought trouble.
current trunk version also has that.
memcached_clone does connect before setting sasl options.
final approach we took and it tested OK:
behavior.cc (memcached_behavior_set):
case MEMCACHED_BEHAVIOR_BINARY_PROTOCOL:
if(ptr->flags.binary_protocol != bool(data)) {
send_quit(ptr); // We need t shutdown all of the connections to make sure we do the correct protocol
}
memcached.cc (memcached_clone):
if (LIBMEMCACHED_WITH_SASL_SUPPORT and source->sasl.callbacks)
{
if (memcached_failed(memcached_clone_sasl(new_clone, source)))
{
memcached_free(new_clone);
return NULL;
}
}
if (memcached_server_count(source))
{
if (memcached_failed(memcached_push(new_clone, source)))
{
return NULL;
}
}
no, that alone brought trouble.
current trunk version also has that.
memcached_clone does connect before setting sasl options.
final approach we took and it tested OK: behavior_ set): BEHAVIOR_ BINARY_ PROTOCOL: ptr->flags. binary_ protocol != bool(data)) { quit(ptr) ; // We need t shutdown all of the connections to make sure we do the correct protocol
behavior.cc (memcached_
case MEMCACHED_
if(
send_
}
memcached.cc (memcached_clone): WITH_SASL_ SUPPORT and source- >sasl.callbacks ) failed( memcached_ clone_sasl( new_clone, source))) _free(new_ clone);
if (LIBMEMCACHED_
{
if (memcached_
{
memcached
return NULL;
}
}
if (memcached_ server_ count(source) ) failed( memcached_ push(new_ clone, source)))
{
if (memcached_
{
return NULL;
}
}