Step 3: Everything is OK according to documentation, but...
Expect
It would be nice if server_id, service_id, client_id, tcUrl, stream_url, stream_id have been of the same variable naming case: either camelCase or snake_case.
Additionally, there is pageUrl property in on_play event.
I propose using snake_case and renaming tcUrl to tc_url and pageUrl to page_url to avoid converting other properties to camelCase.
The tcUrl and pageUrl properties are specific keywords in RTMP and should not be altered in style. However, other properties should follow the style guidelines of SRS.
Description
Please description your issue here
SRS Version: 5.0.0
SRS Log: -
SRS Config:
Replay
Please describe how to replay the bug?
Step 1: Set up any HTTP callback to your server on any event, e.g.
on_publish
Step 2: Look at the payload SRS had sent to your callback applicationStep 3: Everything is OK according to documentation, but...
Expect
It would be nice if
server_id
,service_id
,client_id
,tcUrl
,stream_url
,stream_id
have been of the same variable naming case: either camelCase or snake_case.Additionally, there is
pageUrl
property inon_play
event.I propose using snake_case and renaming tcUrl to
tc_url
and pageUrl topage_url
to avoid converting other properties to camelCase.