Adam

Yeah, that will probably get the project closer to safety. I was testing the water with this issue before committing to code. I have already started three branches: 1. Splitting...

True enough. The points still stand though. Much of the thread-safety issues highlighted stem from the API internals improperly notifying delegates on the wrong queues. And although I do agree...

Seems we're all on the same page: no explicit thread-safe API, but promote defensive coding practices. It helps a lot that the class already has 3 running queues. That fact...

There is some funk remaining, like the shared externs. This is an incremental commit on the way to moving the response-specific parsing into the response class. (so it will get...

Note: _should not be merged if #25 is accepted_

Usage note: this implementation requires that you run an Autobahn test server locally. Everything is default per the Autobahn install and usage guide. just install and `wstest -m fuzzing server`.

@daltoniam I pulled in your branch from #25 (queue-based). There is a problem. Sometimes the `didReceiveString` callback is triggered with `nil` as the string – ostensibly because of some new...

I've also got a bunch of changes for that branch almost ready. Want to wait for those please? Edit: Gah, they're pushed. Ok

Yeah..... lot of great stuff in there actually. But it still fails the Autobahn high-performance tests. I haven't had time to fix it and probably won't for quite a while....

I did search first, but then... #149