>> An RPC with a version vector or something more reliable than a text >> string has already been discussed >> and is presumably going to be in the offing. > > So the options for introducing the GiveUpAllCallBacks are: > > a) Wait for the version vector RPC
no benefit til new stuff is deployed > b) Do something with the version string in the meantime i'm not wild about this. > c) Just state that 1.4.5 is "too old" to bother possibly that being today. > d) The GetStatistics64 RPC trick > Even if I as time goes more and more tend to c), the b) or a) options > give the client a chance to nag about upgrading if such servers are > still out there. i hear someone has an "afs version" census tool. I wonder what Andrew Bacchi thinks :) -- Derrick _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
