libcloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Hoenig (Updated) (JIRA)" <j...@apache.org>
Subject [dev] [jira] [Updated] (LIBCLOUD-114) Provider HTTP Error responses need to be propagated in a better way.
Date Mon, 26 Sep 2011 22:19:12 GMT

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

Brian Hoenig updated LIBCLOUD-114:
----------------------------------

    Attachment: LIBCLOUD-114.patch
    
> Provider HTTP Error responses need to be propagated in a better way.
> --------------------------------------------------------------------
>
>                 Key: LIBCLOUD-114
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-114
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brian Hoenig
>            Priority: Minor
>         Attachments: LIBCLOUD-114.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently when a provider returns an unexpected (error) response the response code and
message must be parsed from a message string in a base Exception.  Instead we should include
the error code and error message in an exception class (ProviderHTTPResponseError).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message