-
Notifications
You must be signed in to change notification settings - Fork 2
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
Meetings fix + some refactoring #130
Conversation
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.
Bro is a legend 🗿
A little problem: |
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.
ok
I agree, I'll fix it quickly |
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.
good job
Meetings are stored in the database as nodes (
(u:User)-[:IS_IN_MEETING]->(m:Meeting)
).Meetings are first created using the "Create a meeting" button and then a friend can join it by clicking the camera button in the friends list.
You can't join if there's no meeting created or you're not a friend of the user (not tested).
The meetings are still unstable as ever...
Sockets are stored as nodes instead of attributes (
(u:User)-[:CONNECTED_TO]->(s:Socket)
).They are created when a user is logged in and removed when the browser tab is closed.
Video call data is shared only to users which are in a meeting with a user by using socket rooms.
Chat messages are sent to all users' devices if the page is open on any of them.
The chat box scrolls down to show the newest message.