On 27 Sep 2011, at 03:15, Jeffrey Hutzelman <[email protected]> wrote: > On Fri, 2011-09-02 at 12:06 -0500, Andrew Deason wrote: >> On Fri, 2 Sep 2011 13:39:13 +0100 >> Simon Wilkinson <[email protected]> wrote: >> >>> Apologies for not raising this earlier, but I have a small question >>> about naming in the 64 bit time draft. I'd really like to use these >>> times for on-the-wire values in rxgk - in particular for token times. >>> Does it seem like a layering violation for something at the RX level >>> to depend on types with AFS in their name? >> >> Are they used in an XDR stream in rxgk? My thoughts on this are that the >> types described in afs3-type-time are XDR types and aren't really for >> use in e.g. general packet headers; so if you're just using a 64-bit >> wide field in a packet or something, these types shouldn't be used >> anyway.
They are used in XDR encoded elements, yes. >> >> But either way, I think we need to be reasonable about using the exact >> same types everywhere; we can use the same format without saying the >> same exact type name. I've come round to this way of thinking, too, so consider this concern satisfied! Cheers, Simon_______________________________________________ AFS3-standardization mailing list [email protected] http://lists.openafs.org/mailman/listinfo/afs3-standardization
