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
We could easily build this on top of the tag based filters. The events would be tagged with a prefix like t:myhome/groundfloor/livingroom/temerature unless we want to expand the api in EventSourcedBehavior.
Filters can be defined with a new topic filter (maybe just implemented on top of tag filters) which may contain wildcards that are matched when evaluating the filter criteria.
It would still only be for one specific entity type (stream id).
The text was updated successfully, but these errors were encountered:
Subscription filters based on topic hierarchies and wildcards are very common. For example MQTT topics https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices/ or NATS topics https://docs.nats.io/nats-concepts/subjects
We could easily build this on top of the tag based filters. The events would be tagged with a prefix like
t:myhome/groundfloor/livingroom/temerature
unless we want to expand the api in EventSourcedBehavior.Filters can be defined with a new topic filter (maybe just implemented on top of tag filters) which may contain wildcards that are matched when evaluating the filter criteria.
It would still only be for one specific entity type (stream id).
The text was updated successfully, but these errors were encountered: