Erik Little
Erik Little
Because I'm trying to do this with one client, and it's getting confusing.
ACKs will come after #10 is merged, or possibly during that merge.
Acks will most likely have the form of ``` swift socket.on("ackEvent") {data in if let str = data as? String { println("Got ackEvent") assert(str == "gakgakgak", "Failed ackEvent") } socket.emit("ackTest",...
#10 adds ACKs
Reopening to track compression
It'd depend on the WebSocket dependency
For your path try `"/socket/"`
I got that too on OS X, I think it's Apple's security enforcing SSL. Not sure how to turn it off.
Yeah, the reason I did that is because variadic parameters have to be last. And I didn't like having the timeoutAfter before the emit data.
I don't think this makes sense. socket.io by default will use http polling before it switches to WebSocket. And you can't point this to an arbitrary WebSocket server, because it's...