Hi On 10/25/2008 09:10 PM Jérôme Renard wrote: > Tobias Schlitt a écrit : >> Hi!
>> While working on the lock support I now dealt with purging of locks. >> This part looks to be quite complex and would need to be done on almost >> every request. It means very much overhead and IMO should not be done in >> request processing itself. > Can you please describe what is done ? You need to check all affected resources (aka files and directories) for locks. Each lock has a base (the resource where it was originally be issued to), which needs to be determined and fetched. If the lock expired (no client did use the lock for timespan X), the lock needs to be removed from all affected resources. In worst case, this could mean to iterate over the complete backend. >> I'd suggest to add a maintanance script to the Webdav component, which >> must be called by the administrator of the server periodically. The >> script locks the backend, goes through all locks and purges those that >> are orphan. > How often do you think this cronjob should be run ? > Can it only be run on nights ? That depends on how it turns out that clients behave and how the infrastructure is. The script would access the lock plugin through some API that we could later also expose to the user, so we can integrate "remove a specific lock" functionality into eZ Publish. Regards, Toby -- Mit freundlichen Grüßen / Med vennlig hilsen / With kind regards Tobias Schlitt (GPG: 0xC462BC14) eZ Components Developer [EMAIL PROTECTED] | eZ Systems AS | ez.no -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
