-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Erizo Controller refactoring to add Clients and Channels #1041
Erizo Controller refactoring to add Clients and Channels #1041
Conversation
It would be nice to catch the socket disconnection event and pass it to clients just to be able to close p2p connections. |
@kekkokk thanks for the heads up! will add a fix to this PR |
@kekkokk done, can you check it please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great refactoring!
rpcPublic[body.message.method].apply(rpcPublic, body.message.args); | ||
try { | ||
rpcPublic[body.message.method].apply(rpcPublic, body.message.args); | ||
} catch(e) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
if (socket.room.streams[streamId]) { | ||
delete socket.room.streams[streamId]; | ||
} | ||
callback(true); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will miss these lines here... ;)
Description
Some code refactoring in Erizo Controller. Now we use the next models to improve code readability:
Changes in Client or Server public APIs
Not needed. All changes are in the backend.
[] It includes documentation for these changes in
/doc
.