Re: How cache invalidations work (and hack to listen in) (was Re: Applause for ZODB! And a question: How do you get pending change info from a transaction object?)

On Mon, May 7, 2018 at 8:52 PM, David Pesta <[email protected]> wrote:

> Hi Jim,
>
> No worries. I tried tinkering with the hack some more and may continue to
> give it another try. But this isn't an urgent emergency for me and I can
> wait for the API to solve it. It's going to be really great when the day
> comes that I can get all this into place! Thank you very much for so much
> effort over the years. This is fabulous technology.
>

Thanks.

It's possible that the API will have the same limitation.  The API may
explicitly warn against calling back into ZODB from subscribers in the same
(logical) thread.  The alternative would be to add too much complexity and
application assumptions in the API.

Jim



>
> Thanks again,
> David
>
> --
> You received this message because you are subscribed to the Google Groups
> "zodb" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jim Fulton
http://jimfulton.info

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.