We've been using it for 6month, much better than the regular Memcache extension. Only issue so far, was caused by the Suhosin patch, when we were passing any parameter to the constructor, sometime it was causing memory problem resulting on a Fatal Error: canary mismatch on efree() - heap overflow detected
But not big issue, passing the persitent id is usefull if you instanciating a lot of Memcached object and you want them to share the same connection, but i highly recommand to extend Memcached to implement a Singleton logic, works better and remove the risk of having that issue. On Jan 28, 11:56 pm, nEosAg <[email protected]> wrote: > I am using Memcache library but having issues in achieving Atomic > operations or to keep integrity of the data. > > To achieve integrity and atomicity i am using pseudo lock operations. > Adam Lee suggested me to use CAS if i need to implement Locking but it > is not supported in Memcache Library. > > Please suggest me which library to use.. > > Waiting for a favourable reply. > > Regards, > Sagar
