jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCLOUDS-398) async api is deprecated, but main docs suggest it is the best api to use
Date Wed, 01 Apr 2015 20:58:53 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Gaul resolved JCLOUDS-398.
---------------------------------
    Resolution: Fixed
      Assignee: Jeremy Daggett

Fixed by 4ecb286208def34b55229d0acc9ae9e882720547.

> async api is deprecated, but main docs suggest it is the best api to use
> ------------------------------------------------------------------------
>
>                 Key: JCLOUDS-398
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-398
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.6.3
>            Reporter: Erik Hetzner
>            Assignee: Jeremy Daggett
>
> The blobstore user guide suggest that the async api is the greatest. Jira, on the other
hand, marks it as deprecated. It would probably be best to change the docs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message