rainbownapkin/canopy
1
0
Fork 0
Code Issues 2 Pull requests Actions Packages Projects Releases Wiki Activity

Added comment relating to issue #57 since it keeps coming up.

Browse source
This commit is contained in:
rainbow napkin 2024-12-10 19:37:19 -05:00
parent f8efe5b99e
commit 47d9aac8f3
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
src/app/channel/connectedUser.js
View file

@ -40,6 +40,12 @@ module.exports = class{
}); });
} }
//My brain keeps going back to using dynamic per-user namespaces for this
//but everytime i look into it I come to the conclusion that it's a bad idea, then I toy with making chans namespaces
//and using per-user channels for this, but what of gold or mod-only features? or games?
//No matter what it'd probably end up hacky, as namespaces where meant for splitting app logic not user comms (like rooms).
//at the end of the day there has to be some penance for decent multi-session handling on-top of a library that doesn't do it.
//Having to crawl through these sockets is that. Because the other ways seem more gross somehow.
emit(eventName, args){ emit(eventName, args){
this.socketCrawl((socket)=>{socket.emit(eventName, args)}); this.socketCrawl((socket)=>{socket.emit(eventName, args)});
} }