Filters: Are Path & Method Filters Available For All Events/Subscriptions?

[austencollins]

Right now, the Event Gateway appears to only allow for path and method filtering in the case of an http Event (at least that is how I read the specification now). However, it seems these are filtering options which could be leveraged for all events.

This is because data on how the Gateway receives the Event is accessible regardless of the Event, and without deserialization of the core data. The path, method, and possibly event name (if it's included in a header or recognized as an HTTP event) are all known at the time of ingestion.

If the Event Gateway can offer a singular experience for all Events, the user experience is much better since happenstances lead to accidental surprises and complexity. Plus, it seems path and method filtering can work for all Events and add value to all of them.

[austencollins]

Related: #153