{"action":"created","issue":{"url":"https://api.github.com/repos/ideegeo/Daemonise/issues/7","labels_url":"https://api.github.com/repos/ideegeo/Daemonise/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/ideegeo/Daemonise/issues/7/comments","events_url":"https://api.github.com/repos/ideegeo/Daemonise/issues/7/events","html_url":"https://github.com/ideegeo/Daemonise/issues/7","id":49846523,"number":7,"title":"RabbitMQ plugin doesn't preserve the correlation_id message property","user":{"login":"ferrouswheel","id":120327,"avatar_url":"https://avatars.githubusercontent.com/u/120327?v=3","gravatar_id":"","url":"https://api.github.com/users/ferrouswheel","html_url":"https://github.com/ferrouswheel","followers_url":"https://api.github.com/users/ferrouswheel/followers","following_url":"https://api.github.com/users/ferrouswheel/following{/other_user}","gists_url":"https://api.github.com/users/ferrouswheel/gists{/gist_id}","starred_url":"https://api.github.com/users/ferrouswheel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ferrouswheel/subscriptions","organizations_url":"https://api.github.com/users/ferrouswheel/orgs","repos_url":"https://api.github.com/users/ferrouswheel/repos","events_url":"https://api.github.com/users/ferrouswheel/events{/privacy}","received_events_url":"https://api.github.com/users/ferrouswheel/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2014-11-24T00:24:20Z","updated_at":"2015-02-10T04:38:42Z","closed_at":"2015-02-10T04:38:42Z","body":"It is reasonably common practice when doing RPC over rabbitmq to use a `correlation_id` to match up response with requests.\r\n\r\nDaemonise doesn't preserve the `correlation_id`, instead assuming every reply has it's own queue. It'd be nice if it would copy this property to the response message if it exists to allow interoperability with other messaging systems that expect this convention to be used.\r\n\r\nFrom rabbitmq's own tutorial https://www.rabbitmq.com/tutorials/tutorial-six-python.html -\r\n\r\n> In the method presented above we suggest creating a callback queue for every RPC request. That's pretty inefficient, but fortunately there is a better way - let's create a single callback queue per client."},"comment":{"url":"https://api.github.com/repos/ideegeo/Daemonise/issues/comments/73643278","html_url":"https://github.com/ideegeo/Daemonise/issues/7#issuecomment-73643278","issue_url":"https://api.github.com/repos/ideegeo/Daemonise/issues/7","id":73643278,"user":{"login":"nupfel","id":44248,"avatar_url":"https://avatars.githubusercontent.com/u/44248?v=3","gravatar_id":"","url":"https://api.github.com/users/nupfel","html_url":"https://github.com/nupfel","followers_url":"https://api.github.com/users/nupfel/followers","following_url":"https://api.github.com/users/nupfel/following{/other_user}","gists_url":"https://api.github.com/users/nupfel/gists{/gist_id}","starred_url":"https://api.github.com/users/nupfel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nupfel/subscriptions","organizations_url":"https://api.github.com/users/nupfel/orgs","repos_url":"https://api.github.com/users/nupfel/repos","events_url":"https://api.github.com/users/nupfel/events{/privacy}","received_events_url":"https://api.github.com/users/nupfel/received_events","type":"User","site_admin":false},"created_at":"2015-02-10T04:38:42Z","updated_at":"2015-02-10T04:38:42Z","body":"finally implemented in https://github.com/ideegeo/Daemonise/commit/f6d378e0366cea2b53c0287f36991f29f7294b20"}}