we use zsyncer to push from a dev machine to a production machine. We sometimes see this behavior: 1) zsyncer reports success. 2) going to the production machine and viewing the management edit form for the object in question shows the old version. 3) eventually the new stuff seems to come up. The interesting thing is that the production system is simple ZEO cluster. All the ZEO clients are exposed to the web via a loadbalancer which presents a single service address to the world. Zsyncer is pointed at the service address to increase the chances that there's always a live server there. But this means that we don't know which production ZEO client actually receives the sync request. I suspect that what happens is: * we sync to http://production/our_zsyncer * we actually sync via the loadbalancer to http://production_1/our_zsyncer * we go to view it at http://production_2/our_zsyncer * we see the old data for a while So I'm wondering: how does a ZEO client know when to reload the object from teh storage? Are there situations in which this doesn't happen "right away"? -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's TENSILE CONJURER STOOL! (random hero from isometric.spaceninja.com)