source: trunk/third/oaf/docs/id-format.txt @ 15503

Revision 15503, 1.1 KB checked in by ghudson, 24 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r15502, which included commits to RCS files with non-trunk default branches.
Line 
1        The Implementation ID (IID)
2
3These are strings that uniquely identify an implementation. The only
4restrictions on these are that they be ASCII, begin with "OAFIID:",
5and not contain the comma (','), square bracket ('[]'), or forward
6slash ('/') characters.
7
8If you are really at a loss on how to create these, here is a suggested format:
9        OAFIID:program_name:UUID
10(where UUID is a uuid as generated by uuidgen).
11
12The only absolute requirement about these is that they uniquely
13identify an implementation. Human readability is a "would be very
14nice" goal.
15
16        The Activation ID (AID)
17
18These are strings that tell how to bootstrap a specific object
19instance. This means that environmental information such as hostname,
20user, etc. They have the following format:
21
22OAFAID:[IID,user,host,domain]
23
24IID format has been described above. 'user' is the login
25username. 'host' is a DNS domain name or stringified IP
26address. 'domain' is a string describing what use area the object has
27- normally this will be 'user' (XXX not clearly defined yet).
28
29Manual creation of AIDs is unsupported - instead, just store and use
30the ones returned by the activate() operation.
Note: See TracBrowser for help on using the repository browser.