-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wichert Akkerman wrote:
>> I wouldn't go there, myself: among other things, you lose the ability >> to do coordination with repoze.retry (e.g., on Postgres' equivalent to a >> ConflictError). > > I'm not sure why you would loose that. I've never used repoze.retry, so > perhaps I'm missing something. Could you expand a bit on that? repoze.retry does what the Zope publisher does on ConflictErrors, but can be configured to catch other exceptions besides ConflictError: PGSQL has an optimistic concurrency mode which raises a simliar exception. You can also tweak the number of retries. Wiring tm2 into the app makes it impossible to configure retry in the "correct" place via PasteDeploy: you would have to hardwire *it* into the app as well (retry needs to be between tm2 and the app). Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktE6dMACgkQ+gerLs4ltQ7JfQCfb69Hjb7rsxxvwUghgdgeQIB3 HT8AoLfkHEB+f5xLOVlaXfH4xPMPF7MI =TAOJ -----END PGP SIGNATURE----- _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
