[
https://issues.apache.org/jira/browse/LIBCLOUD-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809293#comment-13809293
]
Tomaz Muraus commented on LIBCLOUD-418:
---------------------------------------
Quick recap from the IRC discussion:
1. This approach is not ideal because it results in an additional HTTP request
on a lot of calls. Since locations which are available to an account don't
change that often or at all, one thing we could do is simply cache
list_locations response in memory.
2. A lot of methods which now call this new method allow user to pass in a
custom location object, but those new changes don't support that. This new
method simply always check a first location.
This method should be refactored to support checking custom locations which
gets passed to it. Then other code should be updated to do that in case user
passes in a custom location object.
> Better handling of basic and advanced zone differences
> ------------------------------------------------------
>
> Key: LIBCLOUD-418
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-418
> Project: Libcloud
> Issue Type: Bug
> Environment: Some extension functions are only valid for advanced
> zone. There needs to be better handling of zones and different tests for both.
> Reporter: sebastien goasguen
> Attachments: libcloud-418.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
