Justin Karneges

Hi, thanks for the comment. I took at look at your benchmark, and I think we are measuring different things. My goal was to understand the overhead of doing I/O....

I like the idea of comparing to tokio. I'd need to think about how to do it though. My implementation runs the I/O reactor and executor in the same thread.

Yes, but I don't see a way to specify where to run the reactor code. Basically, I need to run `FakeReactor::poll` whenever all futures have returned `Poll::Pending`. It would be...

I discovered that the `LocalPool` executor from futures-rs has a `run_until_stalled` method, which makes it possible to run a reactor in the same thread. I've added a benchmark for that...

The problem with trying to put the reactor in a future is it needs to run only after all other futures have reported pending. It might be possible to relax...

A basic version of this is implemented in the develop branch. It doesn't have any args and always recovers all subscribers.

Correct. For publishing to specific connections, you could subscribe using the connection ID as the channel, but this is not done automatically.

By default, Pushpin’s control port is 5561, so double check you’re specifying the correct port.

Clients connect to a front port (7999 by default) not the control port. The reason for multiple ports is because the control port is private, to be used from the...

Where is `/ws` routing to? If it's the test handler, you need to publish to channel `test`. If it's routing to your backend server, then your server needs to send...