On Thu, 10 Jan 2013, Benjamin Kaduk wrote:
We could rename the member variables to work around, of course, but I think I prefer to add the new types RXGK_Levels and RXGK_Token. I'd also add an
And right after I send I remember that RXGK_Data is already a variable-length opaque value and will work fine for the token type as-is. There must be a typo where we were using RXGK_Data token<> in RXGK_Response.
RXGK_enctype typedef for use in the TokenInfo (and ClientInfo) struct, instead of hardcoding int. (My motivation for not adding this type earlier was the same as in the quoted text above, the concern with having types differing by one character.)
_______________________________________________ AFS3-standardization mailing list [email protected] http://lists.openafs.org/mailman/listinfo/afs3-standardization
