Page MenuHomePhabricator

Support proper continuation for RCStream after connection drops
Closed, DeclinedPublic

Description

Right now there is no concept of continuation in case the Redis stream drops, or if the user loses connection to the RCStream server.

Kafka has a much better protocol for this, though exposing it over the public internet may be unwise. Depending on what approach scales best we may not want each stream listener to have its own Kafka identifier, but rather maintain that pool of subscribers and offsets on the RCStream side.

Event Timeline

Krinkle created this task.Oct 7 2015, 8:40 PM
Krinkle raised the priority of this task from to Medium.
Krinkle updated the task description. (Show Details)
Krinkle added a project: EventStreams.
Krinkle added a subscriber: Krinkle.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 7 2015, 8:40 PM
Aklapper renamed this task from Support proper continuation for RCSteam after connection drops to Support proper continuation for RCStream after connection drops.Oct 8 2015, 8:13 AM
Aklapper set Security to None.
Krinkle moved this task from Backlog to Backlog on the EventStreams board.Oct 27 2015, 9:09 PM
Krinkle closed this task as Declined.Jan 30 2017, 10:55 PM

I'm closing this task since new features are no longer added to RCStream. The new event streams will provide continuation from the start T130651: EventStreams.