reason for templocks?

[howeverking]

Let me know if there's more appropriate place where I can communicate with you (developers)
Ive been looking over the codes and the usage of templock is not clear to me.
All methods are starting with getting a templock and releases it afterwards.

It does not protect a resource since they are shared locks.
2.
Actual locking is done by regular locks.

I don't know why there need to be templocks and
why all methods are starting with getting a templock.

Can you please clarify it?

[ceefour]

From Daniel Jihoon Koh:

Hello.

I've inspected the WebdavServlet codes and could not get a clear idea
why temp locks are used.

I couldn’t find a proper place to ask this question,
I have even posted an issue on
https://github.com/ceefour/webdav-servlet/issues?state=open
but it’s not being responded,
so here I am writing you this e-mail asking this question.
Let me know if there’s more proper place or person I should ask about it.

As far as I know, temps locks are not required by webdav spec,
and I see it is trying to do an internal logic to protect the resource.
Every methods start with getting a temp lock (creating nodes) and release the lock afterwards.
However, since they are shared locks,
they do not protect the resource from other clients…

Can you please clarify why temp locks are used?

I hope to hear from you soon.

Thank you!! :)

[ceefour]

I'm sorry, I'm not the maintainer of web-servlet project which is actually in http://sourceforge.net/projects/webdav-servlet/