On Jun 21, 8:05 am, obp <[email protected]> wrote: > As part of my work i been doing some testings working with the key- > value database TokyoTyrant using your own MemcachedClient.
Are you referring to the spymemcached java client? > I found one > critical issue that caused the client to work improperly. > The second parameter sent in the response from TokyoTyrant is 0 > representing successful request while the MemcachedClient interpreter > this parameter as whether the stored data is serialized or not. > This miss-interpretation caused a serialized data not to be > deserialzied by the client. Can you give a more concrete example? It sounds like you're talking about flags. > Other then this problem, the MemcachedClient have been favorited to > use so i have made some quick & dirty fix ignoring the specified > parameter and assuming all stored data is indeed serialized. > > If i missed anything or got something wrong please correct me, other > then that i just wanted to inform you on this subject in case you > would wish to make an official version who can handle the TokyoTyrant > database. If something makes use of the memcached protocol, we'd certainly prefer it be correct from all client points of view. Whether there's a client issue or a server implementation issue here will advise us as to what needs fixed. :)
