self is dropped in the callbacks

[sergeych]

It is actually a bug in the eventemitter gem, and serious one. Event callbacks for the socket are called on the wrong context, set by the emitter. It took me several hours to trace. I suggest to fix emitter or refrain of using it.

Sample:
`
me = self
@ws = WebSocket::Client::Simple.connect(ws_url)

@ws.on(:open) {
if me != self
puts "\n\n\nSelf is set to wrong in the callback in #{RUBY_VERSION}\n\n\n"
end
}
`

[SpComb]

Workaround is to set a base = self local, and then use base.foo in the callback blocks.

[sergeych]

sure. but first you somehow need to know the problem exists, it is not what you expect from a ruby code. I once lost 4 hours struggling to cope with the same bug in early rails...

[Xasin]

Dang, the same issue just got me.
I was just about to get annoyed at this gem for manipulating self, but if it's a bug from a different gem ...

Thank you for the fix suggestion! That is a really annoying bug though.

[unasuke]

@sergeych This repository was moved ruby-jp/websocket-client-simple. If you still need this, make pull request or issue to ruby-jp/websocket-client-simple again, thx.