From 47d9aac8f36fa363f9d32d969672a1f446ab8224 Mon Sep 17 00:00:00 2001 From: rainbow napkin Date: Tue, 10 Dec 2024 19:37:19 -0500 Subject: [PATCH] Added comment relating to issue #57 since it keeps coming up. --- src/app/channel/connectedUser.js | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/app/channel/connectedUser.js b/src/app/channel/connectedUser.js index b4747cd..3f444c0 100644 --- a/src/app/channel/connectedUser.js +++ b/src/app/channel/connectedUser.js @@ -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){ this.socketCrawl((socket)=>{socket.emit(eventName, args)}); }