When MongoDriver needs to reinitialize, it can sometimes enter a state where it no longer processes change events until a driver method (like flush()) is called, which rouses it from its slumber and causes it to resume processing change events.
This implementation technically obeys the BoskDriver contract, because implementations are allowed to buffer changes indefinitely, but it's fair to say this behaviour isn't ideal, and that a healthy BoskDriver ought to be keeping up with bosk changes without prompting.
If there's a simple way to restore liveness without waiting for a driver operation, that would be nice.
When
MongoDriverneeds to reinitialize, it can sometimes enter a state where it no longer processes change events until a driver method (likeflush()) is called, which rouses it from its slumber and causes it to resume processing change events.This implementation technically obeys the
BoskDrivercontract, because implementations are allowed to buffer changes indefinitely, but it's fair to say this behaviour isn't ideal, and that a healthyBoskDriverought to be keeping up with bosk changes without prompting.If there's a simple way to restore liveness without waiting for a driver operation, that would be nice.