Please note it is not safe to lock files over web/HTTP connection.

• The system has no way to know if a user opens a file for viewing or editing. In fact, a lot of times the user himself is not sure about it;
• HTTP connection is really "connection-less", i.e. each HTTP action is independent. The systems doesn't know when editing is finished and when the lock should be released. When you browse a file, and navigate to another file, the system has no way to decide if the previous file is still being used or if it will be used again. If you walk away or close the browser or DriveHQ FileManager, the system doesn't know if you are still using the file or if you will come back soon or not.

There is a much better workaround, you just need to set a rule among your team:

Assuming a project file named project.doc, a user (John) wants to edit it, he renames it to Project-John-Date.doc before starts editing. This way, all other users know that the file is being used by John; Maybe John is not really editing, so they can contact John to find it out. John (or others) can rename the file back.

When John has finished editing, he should change the file name back to Project.doc.