Reconnecting is mean to the object cache

[jimfulton]

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:

https://github.com/zopefoundation/ZEO/commit/44134205c62acc6076934cccdd9ca0c0c53c8cca

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]

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

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

[jimfulton]

You don't? ;)

[jamadden]

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]

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.)