David,
Ignite has to be compatible with memcached binary protocol, and if it's not,
it has to be fixed. I will investigate this deeper and let you know.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Integration-issue-with-enyimmecached-client-tp3136p3164
Val,
No I do not know where there is a better binary protocol specification.
I was just debugging it and found that inconsistency so this is why I pointed
out to help on troubleshooting the issue.
Is there any other specification that ignite uses to interpret the flags out of
the memcached requ
David,
OK, now I get it. I will take a closer look at this.
Do you by any chance know where I can find good description of Memcache
binary protocol? It sounds like you're quoting [1], which is actually text
protocol. It's a different one.
[1] https://github.com/memcached/memcached/blob/master/do
Thank you
David
From: vkulichenko [valentin.kuliche...@gmail.com]
Sent: Monday, February 22, 2016 9:24 PM
To: user@ignite.apache.org
Subject: Re: Integration issue with enyimmecached client
Hi David,
Are you saying that the client sends the value wit
Hi David,
Are you saying that the client sends the value with the boolean type flag
set which causes it to be saved as a boolean in the cache? It sounds like a
client issue, no? Let me know if I'm missing something.
Actually, is it a requirement for you to use memcached client? Can you
switch to
