[JIRA] Resolved: (GRIZZLY-1589) Delete API change(deletion returns true when the key is not found in memcached)

  • From: "carryel (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [JIRA] Resolved: (GRIZZLY-1589) Delete API change(deletion returns true when the key is not found in memcached)
  • Date: Tue, 8 Oct 2013 12:30:17 +0000 (UTC)
  • Auto-submitted: auto-generated


     [ 
https://java.net/jira/browse/GRIZZLY-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

carryel resolved GRIZZLY-1589.
------------------------------

    Resolution: Fixed

fixed.
grizzly-memcached v1.3.2: rev. 65155f629b8affc09130f0ba32dc189deda0450e


> Delete API change(deletion returns true when the key is not found in 
> memcached)
> -------------------------------------------------------------------------------
>
>                 Key: GRIZZLY-1589
>                 URL: https://java.net/jira/browse/GRIZZLY-1589
>             Project: grizzly
>          Issue Type: Improvement
>          Components: memcached
>            Reporter: carryel
>            Assignee: carryel
>
> memcached returns "key not found" if the given key doesn't exist in storage 
> then grizzly-memcached returns false.
> Commonly, users regard "key not found" as a success in deleting operation. 
> And "key not found" should be distinguished from failure operations such as 
> timeout, I/O failures.
> So I think that it is better that "delete" API returns true if the key 
> doesn't exist in memcached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[JIRA] Created: (GRIZZLY-1589) Delete API change(deletion returns true when the key is not found in memcached)

carryel (JIRA) 10/08/2013

[JIRA] Resolved: (GRIZZLY-1589) Delete API change(deletion returns true when the key is not found in memcached)

carryel (JIRA) 10/08/2013
Terms of Use; Privacy Policy; Copyright ©2013-2015 (revision 20150626.29986a4)
 
 
Close
loading
Please Confirm
Close