Hi Colin, Colin Britton wrote: > The core issue is that if you are using a both the descriptors and content > stores then a single slide transaction spans inserts/updates across both > stores, but a db transaction is only within a single store. This creates an > issue since the connections cannot be shared across both stores (as they are > created inside the individual stores), so if you have an incomplete 'PUT' > and need to rollback then the database can be left in a bad state, or if you > are reading and writing the same file from two different threads then you > can get a bad read, or if you have two threads adding files and they both > try to add a directory at the same time, all these can lead to DB contention > or integrity issues.
So at least that problem would go away if the content and descriptors store would get merged into a single class... I do not see any problem doing so. Probably the decision to split the two was not well thought through, but done from the code modularity perspective only. But maybe I'm missing something (again) ;o) -- Christopher Lenz /=/ cmlenz at gmx.de -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
