IHBAGang/movie-night-chat
2
0
Fork 0
Code Issues 5 Pull requests Releases Wiki Activity

Protect the websocket connections in the ircd #4

New issue
Open
opened 2020-05-14 11:50:29 +00:00 by epi · 0 comments
epi commented 2020-05-14 11:50:29 +00:00
Member
Copy link

Currently the IRCd spawns a lot of threads doing various things.
We need to make sure that the access to all the websocket connections is properly guarded.

  • Do we need to have a mutex for each ws-conn?
  • Wrap the low-level WS operations in ws-conn-closed? checks.
    Because a closed socket cannot get open again this should be sufficient.
Currently the IRCd spawns a lot of threads doing various things. We need to make sure that the access to all the websocket connections is properly guarded. - Do we need to have a mutex for each ws-conn? - Wrap the low-level WS operations in `ws-conn-closed?` checks. Because a closed socket cannot get open again this should be sufficient.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: IHBAGang/movie-night-chat#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?