I see. Yes, this is not an easy one as the websocket update mechanism is
already complex enough and probably doesn't have much wiggle room to add
extra layers of data.
A possible solution could be to implement a custom HTTP endpoint which
creates the harbor input and redirects via a 302 HTTP responses to the
freshly created input endpoint.
Some details about using custom harbor endpoints can be found here:
http://liquidsoap.fm/doc-1.3.0/harbor_http.html
Let me know if that makes sense to you..
Romain
2017-05-22 3:18 GMT+02:00 Mark E <[email protected]>:
> On 04/12/2017 02:03 PM, Romain Beauxis wrote:
>
> > You could try to to use the on_connect parameter from input.harbor and
> > pass your parameters as headers.
> >
>
> That won't work, or so it seems. I'm using Webcast.js, and your code
> there uses the Javascript Websocket, from what I understand it's not
> possible to set additional headers when connecting via a JS Websocket.
>
> Any ideas for another approach?
>
> Mark
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Savonet-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
