> > First, a BinaryTime value is smaller than either a UTCTime or a
> > GeneralizedTime value.
> >True, but very weak conpared to the size of the document, ...
> > Second, in many operating systems, the value can be used without
> > conversion. The operating systems that do require conversion can do
> > so with straightforward computation.
> >You need at least some conversion from a BER encoded variable length
> >integer to some value. You don't any indication why you want to compare
> >the date with some local integer value?
> Many values can use used directly. If the endian ordering is different on
> a particular system, then straightforward manipulation is needed. If the
> epoch is different, addition or subtraction is needed to compensate. If
> the granularity is something other than seconds, then multiplication or
> division is needed to compensate. To me, these are "straightforward
- variable length encoding
- substraction or addition,
- multiplications on IBM 3x0 series.
This seems to me at least as straightforward as a few multiplications fo
a character string based, no variable length, no endian issue,
an addition/substraction for UTCTime. ...
On this aspect, I thing we must agree to disagree. One man's
straightforward is obviously not the same as another man's straightforward.