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-c
which is actually text
>protocol. It's a different one.
>
>[1] https://github.com/memcached/memcached/blob/master/doc/protocol.txt
>
>-Val
>
>
>
>--
>View this message in context:
>http://apache-ignite-users.70518.x6.nabble.com/Integration-issue-with-enyimmecached-
lob/master/doc/protocol.txt
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Integration-issue-with-enyimmecached-client-tp3136p3151.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
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
ntext:
http://apache-ignite-users.70518.x6.nabble.com/Integration-issue-with-enyimmecached-client-tp3136p3144.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hello,
Following is the description of the issue as I posted it in gitter.
I have run into an integration issue between ignite memcached interface and
Enyim client implementation. https://github.com/enyim/EnyimMemcached
I am basically evaluating the options for ignite to replace memcached in som
