diff options
| author |  zardoz <zardoz@web> | 2014-07-09 07:07:27 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-07-09 07:07:27 +0000 |
| commit | f75e5d6de0031cd1e2e87d9d8aed53f1634d3187 (patch) | |
| tree | 12701a4a36b500ac1bfacbad9dfd9e7aa9f23fc5 | |
| parent | faa23efd6ce9ab4d1a4f9249f0d02d46feb6ed34 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/__171__Locking__187___files_until_synced/comment_2_0c683547a6178e4303f0b1ed1f5605a5._comment | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/__171__Locking__187___files_until_synced/comment_2_0c683547a6178e4303f0b1ed1f5605a5._comment b/doc/forum/__171__Locking__187___files_until_synced/comment_2_0c683547a6178e4303f0b1ed1f5605a5._comment new file mode 100644 index 000000000..b76f35da5 --- /dev/null +++ b/doc/forum/__171__Locking__187___files_until_synced/comment_2_0c683547a6178e4303f0b1ed1f5605a5._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="zardoz" + ip="134.147.14.84" + subject="comment 2" + date="2014-07-09T07:07:27Z" + content=""" +Yea, it’s basically just the isolated one file that needs «locking», so one could just try a different route. The idea with keeping state on a server sounds like a pretty good idea. I could just «echo» via SSH to my webserver some info on who has the file locked; then I could wrap the program that uses the SQLite3 DB in a script that checks whether it’s safe. +"""]] |