Volatile subscriptions
Kerollmops opened this issue · comments
Clément Renault commented
- refactoring to use
tokio_proto::streaming::multiplex
instead oftokio_proto::multiplex
- current messages are ok as headers, but appeared events could probably be body chunks
- maintaining a subscription by pumping events to a
futures::sink::Sink
, detecting overflows and dropping the subscription
Joonas Koivunen commented
There is already #9. In general, I am not sure if all these issues are needed since there is the README file.
I can try to create smaller tasks in a more "help wanted" fashion.