[go: up one dir, main page]

Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sending data safety #6685

Closed
lab6net opened this issue Sep 30, 2024 · 0 comments
Closed

sending data safety #6685

lab6net opened this issue Sep 30, 2024 · 0 comments

Comments

@lab6net
Copy link
lab6net commented Sep 30, 2024

Hello everyone

I'am quite new to ant server technology. Been using it for last couple weeks to make some simple streaming service with chat feature. For chat i wanted to use data channel that is available in ant server (streaming through webrtc).

Currently in application settings i can enable/disable data transfer, or allow only to send data by publisher, or by all. I would like to have functionality where everybody can receive the data (that is accomplished by setting data channel to "Publisher and all Players") but nobody can send the data except through rest api. This way i can use my own app as a man in the middle to control those messages and block some stuff (im not only sending chat messages but also various events, and i dont want somebody to send those to everybody just py preparing specific message).

So what i have currently is:
Client are receiving data by standard notification in the callback "data_received", then if they want to send message, they are calling ajax request that goes to my app. My app checks if its correct then makes api call to ant rest api to broadcast that message. The only thing im missing is to block connected users to send anything through data channel without verification.

@ant-media ant-media locked and limited conversation to collaborators Oct 1, 2024
@lastpeony lastpeony converted this issue into discussion #6692 Oct 1, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant