{"action":"closed","issue":{"url":"https://api.github.com/repos/NimbusAPI/Nimbus/issues/180","repository_url":"https://api.github.com/repos/NimbusAPI/Nimbus","labels_url":"https://api.github.com/repos/NimbusAPI/Nimbus/issues/180/labels{/name}","comments_url":"https://api.github.com/repos/NimbusAPI/Nimbus/issues/180/comments","events_url":"https://api.github.com/repos/NimbusAPI/Nimbus/issues/180/events","html_url":"https://github.com/NimbusAPI/Nimbus/issues/180","id":58764989,"number":180,"title":"Multicast Request/Response via Topics?","user":{"login":"RyannosaurusRex","id":438357,"avatar_url":"https://avatars.githubusercontent.com/u/438357?v=3","gravatar_id":"","url":"https://api.github.com/users/RyannosaurusRex","html_url":"https://github.com/RyannosaurusRex","followers_url":"https://api.github.com/users/RyannosaurusRex/followers","following_url":"https://api.github.com/users/RyannosaurusRex/following{/other_user}","gists_url":"https://api.github.com/users/RyannosaurusRex/gists{/gist_id}","starred_url":"https://api.github.com/users/RyannosaurusRex/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RyannosaurusRex/subscriptions","organizations_url":"https://api.github.com/users/RyannosaurusRex/orgs","repos_url":"https://api.github.com/users/RyannosaurusRex/repos","events_url":"https://api.github.com/users/RyannosaurusRex/events{/privacy}","received_events_url":"https://api.github.com/users/RyannosaurusRex/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2015-02-24T16:39:36Z","updated_at":"2016-08-15T07:54:13Z","closed_at":"2016-08-15T07:54:13Z","body":"Here's my scenario.  I'm building a SaaS app, where I intend to have multiple tenants have their own handler for a particular request, let's call it `GetProfileRequest`, which is handled by `GetProfileRequestHandler` and returns a `GetProfileResponse`.  I intend for every request and response message to inherit from a base message that contains a `TenantId`.  The `TenantId` essentially acts as a filter for each tenant, so the handlers for each tenant can have different implementations.  Basically it's a multicast request response as described in the docs, but where I don't want multiple handlers even responding unless the TenantId is for them.\r\n\r\nI know I can just use DI inside a single handler and swap implementations out depending on the TenantId or create a completely separate message contract per-tenant, but there's a chance that other handlers would need to be written in Java, or JS, or something else, so I'd like for them to be able to just subscribe directly to ASB and reply accordingly.  Is that currently possible in Nimbus or something that I shouldn't generally be doing?  "}}
{"actor":{"display_login":"DamianMac"}}