You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't believe this is advised as it seems the dtw project (https://github.com/romi/dtw) is using this lock. It may cause issue when integrating plant-3d-explorer and plant-3d-vision.
Moreover, the database is not aware of what is connected to it, so treating specifically the case of the plant-3d-explorer would require implementing some kind of handshake between plantdb and any client for plantdb to know what to do with which client.
This seems to me that it would require a lot of work for seemingly no added benefits to the user.
If the problems comes from bundling the database when running plant-3d-explorer (eg in a zip file) a command such as zip bundle.zip <database> -x <database>/lock can be used.
On the other hand, if dtw removes its need for the lock, then it would be possible to remove the locking mechanism altogether.
No description provided.
The text was updated successfully, but these errors were encountered: