Upayavira wrote:
I'm being a little naughty, as this question relates to webdav, but not
to slide.
I have a webdav implementation that works on all OSes other than OS X.
On OS X, if you open a resource, e.g. foo.doc, immediately afterwards it
tries to load ._foo.doc (or something like that), which is the files
resource fork. It fails, as the resource isn't there, and retries 50
times, meanwhile the process of loading the file hangs for an
uncomfortable amount of time.
Does that not relate to MacOS filesystem handling rather than WebDAV
itself?
A random though is to try to control MacOS to not do resource fork
retrieval for a specific filesystem or mount.
If that can be done at all and if so in system settings or in Java,
I take the liberty to leave to the Mac experts...
I have also seen MacOS (pre-X) mounting UNIX filesystemes with keeping
of all resources in a separate .AppleDouble-directory at the root of
the mount. Maybe that's one small step further as you in your
implementation could separate Mac-specific resource fork requests
(all for the /.AppleDouble tree) from "real" requests.
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
