FHIR Chat · Topic v Messaging event · subscriptions

Stream: subscriptions

Topic: Topic v Messaging event


view this post on Zulip René Spronk (Nov 07 2019 at 09:54):

Catching up on the new way of dealing with subscriptions: MessageHeader.eventURI is effectively the same concept as Topic.url, and Topic is (in the sense of messaging) a trigger event definition. If correct, we may have to go for a redesign of the MessageHeader, or at the least document the fact that MessageHeader.eventURI could be the canonical URL of a Topic resource.

view this post on Zulip Lloyd McKenzie (Nov 07 2019 at 15:46):

I would say that subscription topics are a proper subset of messaging events.

view this post on Zulip René Spronk (Nov 11 2019 at 07:33):

OK, so what would be an example of something that's a messaging trigger event and not a topic/event used for a subscription? You must know of some, because you use the word "subset"..

view this post on Zulip Lloyd McKenzie (Nov 11 2019 at 14:19):

I could send in a complex query as a message. That wouldn't make sense as a topic. I could also request any number of things. Topics must, by definition, be events that can be triggered on the target server.

view this post on Zulip René Spronk (Nov 11 2019 at 15:03):

Agree that queries are a good example: although: why should one not be able to subscribe to some queries as sent to a server? Other than that the overlap is rather substantial, should we merge Topic and EventDefinition ?

view this post on Zulip Lloyd McKenzie (Nov 11 2019 at 15:21):

It doesn't really make sense to subscribe to someone submitting an arbitrary query. We could potentially merge the resources, but we should be able to differentiate what the topic is allowed to be used for - subscription, messages or both.

view this post on Zulip René Spronk (Nov 11 2019 at 15:27):

Well, EventDefintion/Topic could be the reason for creating a Task, and the "if your receive an query of type x (at the server) route it to me" scenario (albeit not a classic subscription scenario) may actually have value. Adding a code of sorts to indicate the intended usage of the Topic/EventDefintion won't do any harm, although personally I don't see a lot of value in it.

view this post on Zulip Lloyd McKenzie (Nov 11 2019 at 15:32):

If a topic isn't flagged as allowed for a subscription, then you can't use it for a subscription. That'll be pretty important to servers who will likely end up hardwiring what topics they support subscriptions for.

view this post on Zulip René Spronk (Nov 11 2019 at 18:44):

that's certainly true.


Last updated: Apr 12 2022 at 19:14 UTC