fafhrd91
commented
9 years ago sockjs is just transport layer, it does not implement concept of rooms and subscriptions (at least it was like that when i developed pyramid_sockjs) so rooms and subscriptions are application level logic, i don't think you need to modify pyramid_sockjs to implement that logic. i'm not planing to do any development on pyramid_sockjs, but i'm happy to give anyone access to repo.
are you planning to implement channels to which one can un-/subscribe similar to "rooms"? or is it that setting up multiple sockjs-routes will do just that? i need some way to namespace sessions in order to filter them prior to broadcasting messages. if i were to fork/pr pyramid_sockjs where would i start to implement this?