Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconnecting is mean to the object cache #20

Open
jimfulton opened this issue May 29, 2016 · 4 comments
Open

Reconnecting is mean to the object cache #20

jimfulton opened this issue May 29, 2016 · 4 comments

Comments

@jimfulton
Copy link
Member

jimfulton commented May 29, 2016

See hysterical discussion here:

https://mail.zope.org/pipermail/zodb-dev/2006-August/010343.html
(ignore the ssl warning -- sorry)

Which led to this change:

4413420

We clear the object cache because we may have objects in the object cache that aren't in the ZEO client cache, which wouldn't be verified as part of cache verification (which we're getting rid of. If we can do quick verification, which involved replaying missed invalidations, then there's no need to clear the object cache. OTOH, if we drop/clear the client cache, then we should clear the object cache as well. We'll need to make sure that notify_connected (new name for notifyConnected) has enough information to know whether to drop the object cache.

@jamadden
Copy link
Member

jamadden commented May 29, 2016

We'll need to make sure that notify_connected (new name for notifyConnected)

I don't see the difference in names...?

@jimfulton
Copy link
Member Author

You don't? ;)

@jamadden
Copy link
Member

Well I do now, now that both original post and my comment have been edited. Sometimes it's good to be the king ;)

So moving away from Java style camelCaps to the currently-more-prevalent-in-Python underscores.

@jimfulton
Copy link
Member Author

Given that this is an internal API, I thought I'd be snakey.

(Camel case came from Smalltalk and was an accident resulting from the character sets used on Xerox workstations.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants