-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is not working with twemproxy #5
Comments
Hi, Twemproxy only support the ASCII protocol, not the binary one. https://github.com/twitter/twemproxy/blob/master/README.md#features |
Thx for your feedback ! I found another erlang driver with support for both protocols. You don't have any plan to support the ascii protocol ? Twemproxy it's pretty cool. |
I'll add it to the roadmap, shouldn't be too hard to support. |
Hello Philippe, Do you have any idea when we can expect this to be implemented ? Silviu |
If I connect directly to memcache server is working fine. If I connect to twemproxy (https://github.com/twitter/twemproxy) is not working. I receive the following error:
anchor:get(<<"foo">>).
{error,tcp_closed}
23:15:39.337 [warning] [anchor] tcp closed
On the same twemproxy server other clients (both memcache php clients) are working fine.
The text was updated successfully, but these errors were encountered: