On 04/01/2013 23:44, Evert Pot wrote:
On 5 jan. 2013, at 00:23, Trey Nolen <[email protected]> wrote:
I looked at changing the SabreDav manually to 1.8, but the changelog
indicated that a lot of backward compatibility had been broken, so I
didn't make the change thinking it may break more than it fixes.
Very little in relation to plain file serving has changed in recent sabredav
versions. So whatever problems 1.6.4 may have, 1.8 will likely as well.
So if there's issues, I'd recommend digging deeper and try to isolate and debug
problematic requests.
Understood - although that's also one of those catch 22s on a fast
moving project: If some fixes are found, then the usual request is to
submit a fix against a recent version...
1.8 has some interesting changed with respect to caldav and osx that I'm
interested in. Hoping that you might be the person to petition for an
update..?!
My limited debugging so far has been quite painstaking - is there a
switch to get decent level debugging out of sabredav?
Likewise Trey, I think you need to snapshot the db every hour or more
regularly, try and narrow down a repro case until you can pin point
something reproducible and then debug from there. Note almost certainly
some of the problems are in the client, so it would be great to try and
narrow as many as possible down
Cheers
Ed W
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
