Issue101

Title fs_location_info encoding unnecessarily complex
Priority required Status resolved-edit-complete
Superseder Nosy List dnoveck, mre, spencer.shepler
Assigned To spencer.shepler Topics

Created on 2006-07-31.07:56:10 by mre, last changed 2006-10-20.19:14:06 by spencer.shepler.

Messages
msg410 (view) Author: spencer.shepler Date: 2006-10-20.19:14:06
included in draft-08
msg404 (view) Author: dnoveck Date: 2006-10-19.12:45:55
Checked into cvs
msg248 (view) Author: mre Date: 2006-07-31.07:56:10
The i-d states:
      
      XDR does not have any means to declare an 8-bit data type, other
      than an ASCII string, and using 32-bit data types would lead to
      significant space inefficiency.

And then describes a way to pack 8 bit unsigned integers, 4 at a time,
into 32 bit unsigned integers.

We've already faced this issue with NFSv4.0 when we introduced UTF-8.
We defined UTF-8 strings as arrays of type opaque.

fs_location_info should be able to do the same.

This is a worthwhile change as it will knock several pages off
the spec.
History
Date User Action Args
2006-10-20 19:14:16spencer.sheplersetstatus: editing -> resolved-edit-complete
messages: + msg410
2006-10-19 12:45:59dnovecksetstatus: need-text -> editing
assignedto: dnoveck -> spencer.shepler
messages: + msg404
2006-07-31 07:56:12mrecreate