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 | |
---|
3 | These are strings that uniquely identify an implementation. The only |
---|
4 | restrictions on these are that they be ASCII, begin with "OAFIID:", |
---|
5 | and not contain the comma (','), square bracket ('[]'), or forward |
---|
6 | slash ('/') characters. |
---|
7 | |
---|
8 | If 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 | |
---|
12 | The only absolute requirement about these is that they uniquely |
---|
13 | identify an implementation. Human readability is a "would be very |
---|
14 | nice" goal. |
---|
15 | |
---|
16 | The Activation ID (AID) |
---|
17 | |
---|
18 | These are strings that tell how to bootstrap a specific object |
---|
19 | instance. This means that environmental information such as hostname, |
---|
20 | user, etc. They have the following format: |
---|
21 | |
---|
22 | OAFAID:[IID,user,host,domain] |
---|
23 | |
---|
24 | IID format has been described above. 'user' is the login |
---|
25 | username. 'host' is a DNS domain name or stringified IP |
---|
26 | address. 'domain' is a string describing what use area the object has |
---|
27 | - normally this will be 'user' (XXX not clearly defined yet). |
---|
28 | |
---|
29 | Manual creation of AIDs is unsupported - instead, just store and use |
---|
30 | the ones returned by the activate() operation. |
---|
Note: See
TracBrowser
for help on using the repository browser.