Fixed bug when 'END' is contained in the cached data

[lusentis]

I have a problem getting cached data if it contains the string "END". I have fixed the problem by replacing .indexOf('END') with .lastIndexOf('END') as suggested in #22

[elbart]

i understand your point but with your fix most of the tests are failing... currently investigating on this problem... i hope to pull this asap since this is surely very useful...

[guileen]

same problem.

[1999]

@elbart any changes on this? i left a comment in #26 regarding this. I hope it helps

[sricc]

Caught this problem as well. Any chance this will be fixed soon?

[masonzhang]

@elbart Please merge this pull request. This fixed my issue.

[1999]

@masonzhang this pull request does not solve the problem completely. Look this comment #26 (comment) and you'll see that. As far as I understand @elbart discontinued the developing of node-memcache project and it's probably better to fork it now.

[masonzhang]

@1999 right, the fix cannot resolve the issue. After long run on server, I saw other error logs. Thanks a lot for the reminder. To further investigate the issue. I output the content of the cache to logs when error happens. Finally I found the reason is, sometimes the string read from cache may contains multiple cached object. The simple fix does not resolve the issue. I didn't read the document of memcached, but I think it should be documented in server protocol.

[jisqyv]

@lusentis See #46 for a different (better) approach.