Hi Greg,
On 1/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> about workitem locking : the whole idea is just to prevent two users > to concurrently edit the same workitem. In memory locking is fine, I > assume you don't need a lock on a workitem to survive a system crash, > the first user in the group to get back at the workitem treats it. Hmm, can you tell me when workitems (their attributes and so on) are persisted then? On proceed/cancel/forward only?
Still speaking in the worklist point of view. The worklist saves/persists a workitem whenever it receives it, a user made a change to it. It deletes the workitem upon successful forwarding (dispatch back to the engine).
> In the vanilla standalone OpenWFE, the worklist doesn't persist locks > on workitems (and never will). If you really need to ensure that > exactly one person uses a workitem, the usual trick is to assign the > workitem to its private inbox... It all depends on the organization. Oh sure. Thanks. And with this, I realize I should actually check why we even lock at all :)
BTW, are you using an embedded worklist or Magnolia participants (users inbox) ? -- John Mettraux -///- http://jmettraux.openwfe.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFE users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwfe-users?hl=en -~----------~----~----~----~------~----~------~--~---
