> yes, I mean conflict, which will take the volume into a WriteDisconnected
> mode? Or not necessary?

As I understand it yes; and then you have to repair the conflict before 
further changes will be propagated to the server. But I'm still new to coda.

> So I was wondering, wont it be good if the server actually checks if the
> file is open rw, only when the volume is Connected in diconnected mode this
> check should be skipped.

Meaning if it's already opened the second process attempting to open it will 
fail?

Of course, that is desirable. But I would personally rather have the full 
support for disconnected operation on both clients and servers. And as long 
as that is supported, any file locking functionality is going to be 
semi-reliable at best, and the question is how useful that would be.

-- 
/ Peter Schuller, InfiDyne Technologies HB

PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller_at_infidyne.com>'
Key retrival: Send an E-Mail to getpgpkey_at_scode.org
E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org