Conflict resolution / PersistentList
Sean Upton <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <CANjV-2NjAR2FbvsSDA4tWH8BSOypcqYO1WAU56yDpoJ+zTen0g@mail.gmail.com> |
I am using a PersistentList to maintain an insertion order (LIFO) of identifiers for another unordered (OOBTree-based) data structure. I'm curious to know if there is any alternative to PersistentList that implements _p_resolveConflict(), say, in a way similar to BTrees buckets? For my use case, order matters; I'm hoping to avoid subclassing PersistentList, but can if I need to. My goal is to know what options are for avoiding a Zope 2 request retry, supposing some requests are expensive enough to make this a problem. Sean -- 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.