Jacob Rief
Jacob Rief
can I close this?
Nope, please read https://tools.ietf.org/html/rfc6455#section-11.3.1 I certainly will not introduce non-standard behavior as a workaround for broken clients.
yes, this certainly.
I did some work on this some time ago. But I'm still unsure, if it does not have unwanted side-effect, when mixing different kinds of publishers/subscribers. Please check this branch...
Wouldn't that make the API far too complicate? How about something simpler, say that the same message is never send back on its counterpart. Say ws4redis receives a message on...
> Maybe we should simply try to get closer to the other implementations (I don't know them though) Me neither. Anybody here? Please give some hints.
Hmm, Interesting idea, but I have two problems with it. How can the client programmatically tell the server how and in what he's interested? With Socket.IO, the client could pass...
I was thinking about how to solve this problem: Each message is prefixed with a number consisting of the current threat/greenlet-ID and a message counter, which is increased after publishing...
@Glideh I just commited a new version on branch **exclude-message-sender**. I hope this now is a good solution: There is a message class which wraps messages into a list with...
I just dropped theses changes. They don't work as expected. Currently the only new feature is that one can choose, if he wants to echo his own message or not.