Github user karkum commented on the pull request:
https://github.com/apache/curator/pull/38#issuecomment-52567036
Hmm, let me make sure I understand:
* In ```InterProcessMutex```, we expose the actual lockPath being used by
the lock (which could be either ephemeral or persistent).
* This would allow any user of ```InterProcessMutex``` to take care of
clean up/notification steps based on whether the lock of that path actually
exists or not.
I think this makes sense, but I'm not sure if it is ideal to expose the
actual lock path used by this recipe. What if a client is using the default
implementation (with ephemeral nodes), then getting the path would be pretty
useless, since that node would be deleted once connection is lost right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
