Discussion: Event+destination terminology query and events with no destination

[leggetter]

From @alexluong:

I think we’re missing a terminology for “event + destination”. When an event is received, it can be matched with 0, 1, or many destinations. Event by itself does not have any destination. But in order for event to have a status, it must have some sort of destination.

In Hookdeck we use:

• Request: inbound request from an event source
• Event: an event that has been generated by the Request and will be delivered to a destination
• Attempt: an attempt to deliver an Event to a destination

Do we need similar terminology in Outpost?

Also, how do we get events from the API that were published but didn't end up being routed to any destination? Or should some other logic occur if this happens? For example, should the event be rejected?

Note: do we want to split this out into two different issues?

[alexluong]

finally done with this!!