Jeff,
I have been looking seriously at the Windows client with the intention
of putting the stage 1 functionality there. I apologize for not
coordinating with you on it previously.
If you'd like to discuss this further, please drop me an email. I'd
like not to interfere with getting a stable 1.4 release out. However,
my understanding from Derrick is that this is a post-1.4 feature, in
general.
Matt
Jeffrey Altman wrote:
I believe Matt is working on implementing something like this for the
Unix/Linux AFS clients. However, no one at the present time is working
on an implementation for the Windows clients which is what you require.
Normally I would be the one to do it but I will not have time to do so
for several months. There are other higher priority efforts that I
must work on:
* helping get the OpenAFS 1.4 release out the door so there is a
truly "stable" Windows release that will not suffer from unfortunate
regressions due to new development
* working on the rxgk security provider so there is the ability to
use something other than single DES for authentication and
data confidentiality
* porting to 64-bit windows
* adding support for the Unicode version of the CIFS/SMB protocol
so that we can have large file support, dfs interoperability,
Unicode path name support, etc.
Byte range locking is important but it is considered to be of slightly
lower priority. In any event, even if I found a few days to implement
it. It would not be in the initial 1.4 release. It would be nice to
get it implemented before the end of the year.
Jeffrey Altman
Daniel Wood wrote:
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
