Changeset 1111 for trunk/LATMOS-Accounts/man/man8/latmos-accounts.pod

Timestamp:

08/09/12 14:59:05 (12 years ago)

Author:

nanardon

Message:

more documentation

File:

• trunk/LATMOS-Accounts/man/man8/latmos-accounts.pod (modified) (2 diffs)

trunk/LATMOS-Accounts/man/man8/latmos-accounts.pod

@@ -28 +28 @@
 Standard users base under Unix system, also used for C<NIS>/C<YP> system.
 
+=item Kerberos/Heimdal
+
+Remote access to Kerberos base.
+
 =back
 
 =head2 WORKFLOW
 
-Link::Accounts is made of three components:
+C<Link::Accounts> is made of three components:
 
 =over 4
@@ -46 +50 @@
 =head3 Bases
 
+A base module provide the common way to access a set of data. Usually a base is
+accessed remotely trought a network connection but always.
+
+In an ideal world, all base can be synchronised over another one.
+
+Each data inside a base is represented as objects of differents type. The most
+common type are for sure C<user> and C<group>.
+
 =head3 Objects
 
+Inside a base the objects is the unbreakble subset of data.
+
+Each object are identified uniquely by both a type and an identifier on the
+C<LATMOS::Accounts> side. This mean two object of different type can have the
+same id.
+
+On the other hand the identifier must allow to identify uniquelly the object
+inside the base.
+
+For example in C</Unix file> base each line of F<passwd> is a C<user> object and
+the login is the uniq identifier.
+
+The couple object type/identifier must also allow to find common objects through
+differents bases.
+
 =head3 Attributes
+
+The attributes is the basic data storage for an object.
+
+Each attribute have a name and normally a specific usage, even through base.
+
+Attributes may have different behavior, depending their definition and base
+constraint:
+
+=over 4
+
+=item single or multiple value
+
+=item limited possible values
+
+=item reference to others objects
+
+=back
 
 =head1 CONFIGURATION