[
https://issues.apache.org/jira/browse/LIBCLOUD-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209571#comment-13209571
]
Dave King commented on LIBCLOUD-153:
------------------------------------
I've attached a file with my first attempt at this.
I think that libcloud not supporting params as a tuple list makes the utility
of the connection objects much lower.
I think long term we would want to get away from params-as-a-dict. I'm not
sure if it's better to just allow the OpenStackBaseConnection to have this
special behavior for now or allow users to pass parameters in as a dict of
lists (but that breaks a lot of things too).
Let me know what you think.
> OpenStack BaseConnection does not allow GET parameters as a key-value pairing
> -----------------------------------------------------------------------------
>
> Key: LIBCLOUD-153
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-153
> Project: Libcloud
> Issue Type: Bug
> Components: Core
> Reporter: Dave King
> Priority: Minor
> Attachments: libcloud-153.patch
>
>
> For GETs, OpenStack BaseConnection assigns the cache-busting attribute on the
> parameters to a random number.
> This assignment is done as a dictionary assignment, meaning it is not
> possible to pass in a value of key-value pairs (the main reason to do this is
> to pass the same key in with different values, for example, as in the batch
> delete at
> http://docs.rackspace.com/loadbalancers/api/v1.0/clb-devguide/content/Remove_Nodes-d1e2675.html
--
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
