{"action":"created","issue":{"url":"https://api.github.com/repos/EasyNetQ/EasyNetQ/issues/455","labels_url":"https://api.github.com/repos/EasyNetQ/EasyNetQ/issues/455/labels{/name}","comments_url":"https://api.github.com/repos/EasyNetQ/EasyNetQ/issues/455/comments","events_url":"https://api.github.com/repos/EasyNetQ/EasyNetQ/issues/455/events","html_url":"https://github.com/EasyNetQ/EasyNetQ/issues/455","id":88578078,"number":455,"title":"I'd like to control the Queue names without including a \"type\" property in my message","user":{"login":"skoon","id":67300,"avatar_url":"https://avatars.githubusercontent.com/u/67300?v=3","gravatar_id":"","url":"https://api.github.com/users/skoon","html_url":"https://github.com/skoon","followers_url":"https://api.github.com/users/skoon/followers","following_url":"https://api.github.com/users/skoon/following{/other_user}","gists_url":"https://api.github.com/users/skoon/gists{/gist_id}","starred_url":"https://api.github.com/users/skoon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/skoon/subscriptions","organizations_url":"https://api.github.com/users/skoon/orgs","repos_url":"https://api.github.com/users/skoon/repos","events_url":"https://api.github.com/users/skoon/events{/privacy}","received_events_url":"https://api.github.com/users/skoon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-06-16T00:49:23Z","updated_at":"2015-06-16T08:08:55Z","closed_at":null,"body":"We have existing queues and I'd like to be able to use the Subscribe methods or even the generic Consume<T> methods without including the deserialized type name as a property of my message.\r\n\r\nIncluding a consumers internal type name breaks the service boundary in a couple of ways and I'd rather not have to include it. I'm fine with an exception being raised if the message cannot be deserialized in to the type I specify in my generic method."},"comment":{"url":"https://api.github.com/repos/EasyNetQ/EasyNetQ/issues/comments/112326664","html_url":"https://github.com/EasyNetQ/EasyNetQ/issues/455#issuecomment-112326664","issue_url":"https://api.github.com/repos/EasyNetQ/EasyNetQ/issues/455","id":112326664,"user":{"login":"mikehadlow","id":223097,"avatar_url":"https://avatars.githubusercontent.com/u/223097?v=3","gravatar_id":"","url":"https://api.github.com/users/mikehadlow","html_url":"https://github.com/mikehadlow","followers_url":"https://api.github.com/users/mikehadlow/followers","following_url":"https://api.github.com/users/mikehadlow/following{/other_user}","gists_url":"https://api.github.com/users/mikehadlow/gists{/gist_id}","starred_url":"https://api.github.com/users/mikehadlow/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikehadlow/subscriptions","organizations_url":"https://api.github.com/users/mikehadlow/orgs","repos_url":"https://api.github.com/users/mikehadlow/repos","events_url":"https://api.github.com/users/mikehadlow/events{/privacy}","received_events_url":"https://api.github.com/users/mikehadlow/received_events","type":"User","site_admin":false},"created_at":"2015-06-16T08:08:55Z","updated_at":"2015-06-16T08:08:55Z","body":"Hi Scott,\n\nThe problem is that there are various places in EasyNetQ where we allow\nmultiple type-specific handlers for a single queue and the only way we know\nwhat the message type is, is by examining the type property.\n\nMike\n\nOn Tue, Jun 16, 2015 at 1:49 AM, Scott Koon <notifications@github.com>\nwrote:\n\n> We have existing queues and I'd like to be able to use the Subscribe\n> methods or even the generic Consume methods without including the\n> deserialized type name as a property of my message.\n>\n> Including a consumers internal type name breaks the service boundary in a\n> couple of ways and I'd rather not have to include it. I'm fine with an\n> exception being raised if the message cannot be deserialized in to the type\n> I specify in my generic method.\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/EasyNetQ/EasyNetQ/issues/455>.\n>\n"}}