Hi Folks,
I have a question about best practices for maintaining the state of a document. In a SQL world, I track document statuses using a control table. I find it useful to likewise track status separately from documents via a status record in MarkLogic so that for example, I don't need to update a document when performing quality control. In addition, I can maintain a set of records to track the history of a document and refer to saved instances of the document at each touch point in a workflow where I really do want to retain a copy of the document whenever a change has taken place as referenced by the current state and document URI as well as other important information such as ownership, date/time stamp, etc. However, there are some asynchronous back-end processing actions that can be taken on the document which can be spawned concurrently with updates made to the status table when each completes. I want to make sure that I understand the concurrency issues related to updates top the status record. I think I can assume that there really won't be any need for a locking mechanism, that is that each response will update the status table atomically. I plan to have separate statuses for each of the asynchronous events as the completion of all such statues will indicate that the record is ready for the next stage. Thanks for any suggestions and insight into this! Tim
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
