Open bwmcadams opened 13 years ago
Was going to use Akka Scheduler for this (change the message from CursorActor to ConnectionChannelActor to just send over a cursor ID to be queued, instead of directly sending the cursor kill; keep a queue of cursor IDs in ConnectionChannelActor; schedule a timeout message to be received by ConnectionChannelActor when the queue is non-empty, and send kill cursor in response to that scheduled message).
That was my thought exactly for how to do it. You can feel free to tackle it if you want, my next plan was to look at Replica Sets.
On Tue, Aug 2, 2011 at 4:24 PM, havocp < reply@reply.github.com>wrote:
Was going to use Akka Scheduler for this (change the message from CursorActor to ConnectionChannelActor to just send over a cursor ID to be queued, instead of directly sending the cursor kill; keep a queue of cursor IDs in ConnectionChannelActor; schedule a timeout message to be received by ConnectionChannelActor when the queue is non-empty, and send kill cursor in response to that scheduled message).
Reply to this email directly or view it on GitHub: https://github.com/bwmcadams/hammersmith/issues/51#issuecomment-1712791
Cursor cleaning needs to be rethought for streaming drivers.
They were removed in the Akka migration.