You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2019. It is now read-only.
I'm using a RESTful API (documented here) for the OpenStack message queue service. I have a complete SPORE spec for it, it works well enough.
My issue is with several types of responses that contain links to other resources; for instance, a common workflow with this API is to "claim" several messages on a given message queue. The server then tags those messages internally with the claim ID so that no one else will be able to claim them and returns a response with the claim ID and the messages.
Now my problem is that although I know in advance what type of resources the various links in the response point to, I cannot call the corresponding client methods with the correct parameters, e.g.
# how can I get the values for queue_name, claim_id and message_id ?$client->release_claim(queue_name=>'tomato', claim_id=>'a28ee94e-6cb4-11e2-b4d5-7703267a7926');
$client->delete_message(queue_name=>'tomato', message_id=>'50b68a50d6f5b8c8a7c62b01', claim_id=>'a28ee94e-6cb4-11e2-b4d5-7703267a7926');
I can sort of get the querystring parameters, but extracting route parameters is going to be much harder. Ideally I'd do something like
I'm using a RESTful API (documented here) for the OpenStack message queue service. I have a complete SPORE spec for it, it works well enough.
My issue is with several types of responses that contain links to other resources; for instance, a common workflow with this API is to "claim" several messages on a given message queue. The server then tags those messages internally with the claim ID so that no one else will be able to claim them and returns a response with the claim ID and the messages.
Now my problem is that although I know in advance what type of resources the various links in the response point to, I cannot call the corresponding client methods with the correct parameters, e.g.
I can sort of get the querystring parameters, but extracting route parameters is going to be much harder. Ideally I'd do something like
I've tried poking around in the internals of Net::HTTP::Spore but I don't believe this is possible without some refactoring.
The text was updated successfully, but these errors were encountered: