-
Notifications
You must be signed in to change notification settings - Fork 3
로비 재진입 시 webrtc 시그널링 재시도 버그 #117
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
The head ref may contain hidden characters: "115-\uB85C\uBE44-\uC7AC\uC9C4\uC785-\uC2DC-webrtc-\uC2DC\uADF8\uB110\uB9C1-\uC7AC\uC2DC\uB3C4-\uBC84\uADF8"
Conversation
interface Release v0.0.1
Hotfix/ci cd 수정
user가 없을 때는 바로 return 하도록 수정
…isconnect되면-서버가-끊어지는-오류-수정 105 hotfix user가 없을 때 disconnect되면 서버가 끊어지는 오류 수정
interface-v0.0.3 webRTC 적용
hotfix - isAuth true로 변경 여부 main Merge
…face into 115-로비-재진입-시-webrtc-시그널링-재시도-버그
…rface into 115-로비-재진입-시-webrtc-시그널링-재시도-버그
|
|
||
| const emitEvent = this.getEventAtEndInterviewByRole(user.role); | ||
| client.to(clientId).emit(emitEvent, { docsUUID }); | ||
| server.to(clientId).emit(emitEvent, { docsUUID }); |
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.
client socket에서는 자기 자신의 소켓이 제외되어 broadcast를 해도 event가 오지 않는거였군요
| useEffect(() => { | ||
| //TODO Lobby 첫 렌더링 시가 아니라 첫 입장 시만 하기 | ||
| startConnection(me.uuid); | ||
| if (!webRTCUserList.has(me.uuid)) startConnection(me.uuid); |
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.
key뿐만 아니라 value까지 체크하면 stream이 끊겼을 때 signaling 과정을 다시 거쳐서 stream을 살릴 수도 있을 거 같네요
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.
일단은 이렇게 진행하고 나중에 생각해보는걸로 합시다.
|
다른 브랜치들을 merge 해서 PR이 복잡해졌네요. 다음부터는 신경써서 하면 좋을 것 같아요 |
PR 목적 / 요약
관련 이슈