Channel handling: have a dedicated event topic per event key

INTERSECT-SDK / python-sdk

Interconnected Science Ecosystem - Software Development Kit (INTERSECT-SDK)

https://intersect-python-sdk.readthedocs.io

BSD 3-Clause "New" or "Revised" License

4 stars 1 forks source link

Channel handling: have a dedicated event topic per event key #13

Open Lance-Drane opened 3 months ago

Lance-Drane commented 3 months ago

Currently, the events channel looks like this:

<organization>/<facility>/<system>/<subsystem>/<service>/events

This publishes all events to a single channel, which has some problems regarding authorization (plus requiring clients to perform excessive control flow branching).

A better approach may be:

<organization>/<facility>/<system>/<subsystem>/<service>/events/<event_name>

where event_name represents an event key.