Versions Compared

Old Version 3

changes.mady.by.user guozhang Wang

Saved on

compared with

New Version 4

changes.mady.by.user guozhang Wang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Users implementing customized session-store would now need to make code changes to add one more function implementation for the added API. The reason that we've decided to not have an default implementation (e.g. have a very conservative range query, and use a condition to filter out all but only leave one that has the exact start/end timestamp) in the public API is that this one is going to be used inside the library as well at critical code paths, e.g. caching store's flush logic. And hence we really need this API implementation to be efficient.

Rejected Alternatives

  1. I've considered adding this API to ReadOnlySessionStore, but realized it is not a very useful API for interactive queries since most IQ users would not know the exact session start-end timestamps.