HttpGetEndpoint / HttpPostEndpoint

[Jason Earl]

I've seen some mention of this, but not seen any solid examples in the docs.

If I was to setup a HTTP end point (namely in node), again using the one2many example as a reference / start point, can I setup a single HTTP end point for the presenter or do I need to create one for each viewer? As it's working in version 5.x is it working like Icecast would (and if so, does the HTTP POST end point work like this too? I'm just thinking it's a lot easier to send streams up using apps like liquidsoap, and anything sort of radio broadcasting apps that support Shoutcase/Icecast), and while it's not as fast as WebRTC, I'm guessing the latency is round 15-30 sec? (I'm guessing this is largely client side as well?)

I'm guessing the GET has been removed in 6.x but it seems the POST end point is still there.... so I presume that will still be supported? From what I've seen in other posts you're leaning towards HLS for the delivery. Will this be encoded in the same sort of codec as the WebRTC end points, or will it be transcoded to something like WebM/H264/AAC which I guess is typically more associated with HLS.

I presume this binds to the port in HttpConfEndpoint.conf.ini setting, rather than to the Node JS instance and the URL is auto generated and returned from getURL?