henry-chris

@BishoyBishai , @akaskj , @tiimoS - I also have this problem. Can we possibly pool knowledge to see if there are any similarities? When I deploy my server everything works...

I am also getting this problem and only in production. It's weird, we have a DEV/QA/Prod environment and it's only happening in Prod. They are all configured the same. We...

@Yaffle I can, thanks. Sadly, my error was due to a bug in our production deployment where my keep-alives weren't getting through in specific instances. Fixing those has alleviated the...

@Yaffle Sorry it's taken me a bit. I see an error message explaining the issue and a call stack. Seems good to me. Since you say 'Reconnecting' I'm guessing I...

I'm new-ish to this library and SSE. I'm wanting to create more of a real-time collaboration app where a group of users subscribe to a Redis pub/sub channel. I wouldn't...

@tpeczek I have been looking at this off and on and "Yes" it seems to need some type of group functionality. I'm still working out the details, but we handle...

@tpeczek I'm not sure how to parse your comment. Building a group is not really a problem. The problem is how to only send specific events to specific groups using...

@tpeczek Right, so if I send my GroupId over with the `HttpRequest` I can catch both the Client and Group with the Connected Event. That's what I'm thinking at least....

@tpeczek, @seniorquico Thanks, yes my trouble was finding the right way to go about this. I wanted to make sure I wasn't spawning a bunch of Background services that weren't...

Just as an update. Everything is working well. I went with a similar approach to what you two suggested. Working well with Redis over 3-4 server nodes with document specific...