FUN!
The int8 attributes don't have anything to mark them as
time stamps or time deltas, you have to hardcode the attribute names into the
applications. That is how adfind does it for those and how LDP does it for those
as well as GUIDs and other attributes[1].
In terms of working with internally, that is by far the
easiest format in my opinion, just keep it UTC. For people to read it isn't so
nice. In that case you may want to instead use a Generalized-Time syntax
(attribsyntax 2.5.5.11 / OMsyntax 24) which can be read by a human without too
much pain. It is the ZULU format that you see with whenChanged, whenCreated, etc
and programs that want to translate it can easily recognize it. It just has to
always specify a time, it can't be an offset like the int8's are used to do like
with the domain policy values, etc. Oh searching for a range of values is a
little easier (or maybe I should just say more intuitive) with int8 as well
versus searching Generalized-Time.
joe
[1] I figured out a generic way to handle GUIDs that
usually correct.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mr Oteece
Sent: Friday, February 03, 2006 2:27 PM
To: [email protected]
Subject: [ActiveDir] Custom date/time attributes in AD/ADAM schema
