Clarification on AdmissionWebhook closing status behavior for HTTP-based outgoing protocols (LLHLS/HLS)

[Mengsreang-Chhoeung]

Hi OME Team,

I am currently architecting a platform using OvenMediaEngine (v0.20.5) and leveraging the AdmissionWebhook feature for viewer lifecycle management and session tracking (direction: outgoing).

The official documentation, the webhook payload includes request.status which can be opening or closing. I am experiencing behavior where the closing event is missing or never triggered for HTTP-based playback protocols like LLHLS or standard HLS.

I wanted to clarify the intended design:

1. Is the closing status for direction: outgoing explicitly unsupported or anything I don't know?
2. If a client stops requesting chunks or closes the player, does OME maintain a internal session timeout that should eventually fire the closing webhook, or is it bypassed entirely?

Thank you for your time and for building an amazing media server!

[getroot]

The closing event was merged earlier through a PR. Since then, the Provider side has been maintained to some extent, but the Publisher side hasn't been. (For one, we're not using this feature ourselves.)

With HTTP-based publishers, noticing the end of a session (guaranteeing it 100%) is a somewhat difficult thing. There's no guarantee that the client will keep the HTTP connection alive; at some point it simply stops downloading. Additional methods like timeouts would need to be introduced to guarantee this. This is on our roadmap, but at a very low priority.