Commit c9866ab
committed
chore(performance): only check permissions when changing content
Avoid setting up the file system for read only shares.
Also clarify the behavior:
Updates are silently dropped as they were before.
Previously `stepsToInsert` would always be empty for readonly requests,
due to the continue in the loop collecting the steps.
So there was no way to trigger the
```
NotPermittedException('Read-only client tries to push steps with changes')
```
Keep this behavior for now so we can backport this commit.
Clients on readonly shares regularly push updates to the server
to update their awareness state - i.e. let others know they are still around.
These requests trigger the addStep function
even if they do not actually change the content of the file.
Signed-off-by: Max <max@nextcloud.com>1 parent 5fc7ed8 commit c9866ab
1 file changed
Lines changed: 3 additions & 8 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
218 | 218 | | |
219 | 219 | | |
220 | 220 | | |
221 | | - | |
222 | | - | |
223 | 221 | | |
224 | 222 | | |
225 | 223 | | |
226 | 224 | | |
227 | 225 | | |
228 | | - | |
229 | | - | |
230 | | - | |
231 | 226 | | |
232 | 227 | | |
233 | 228 | | |
| |||
240 | 235 | | |
241 | 236 | | |
242 | 237 | | |
243 | | - | |
244 | | - | |
| 238 | + | |
| 239 | + | |
| 240 | + | |
245 | 241 | | |
246 | | - | |
247 | 242 | | |
248 | 243 | | |
249 | 244 | | |
| |||
0 commit comments