RTSP conn API should also have path property, like RTMP does

[terion-name]

Describe the feature

RTMP:
https://bluenviron.github.io/mediamtx/#operation/rtmpConnectionsGet

{
  "id": "string",
  "created": "string",
  "remoteAddr": "string",
  "state": "idle",
  "path": "string",
  "query": "string",
  "bytesReceived": 0,
  "bytesSent": 0
}

RTSP:
https://bluenviron.github.io/mediamtx/#operation/rtspConnsGet

{
  "id": "string",
  "created": "string",
  "remoteAddr": "string",
  "bytesReceived": 0,
  "bytesSent": 0
}

Absence of state, path, query fields makes rtsp api literally useless

[aler9]

You are confusing RTSP connections with RTSP sessions.
A RTSP connection is used to initialize a RTSP session.
A RTSP session can be controlled by multiple RTSP connections.
The RTSP session is associated with a path and has all the fields you need.

[terion-name]

oh... sorry, confused because rtmp api uses connections

[terion-name]

@aler9 but it dosn't help in reallity.
in runOnConnect hook I get rtsp connection id. and with current apis I have no way to get session associated with this connection