Re: [Setup-tool-hackers] Fine-grained location management

[Chema Celorio <chema celorio com>]

On 24 Jan 2001 12:09:03 -0500, Bradford Hovinen wrote:
> When a child location partially defines the data for a particular
> backend, it must store only those configuration settings that the user
> explicitly changed when updating that backend's configuration under
> that location. If the frontend simply dumped its entire XML snapshot
> to the log, all of the configuration settings would be reflected in
> that snapshot, and under the method indicated above, partial
> containment would be equivalent to full containment. Therefore, when a
> frontend stores its configuration under partial containment, the

Where/who is destion made about using a partial or full containment ?

I am aslo wondering if this will not confuse users.

For example user has :

Location home 
IP : 1.2.3.4
DNS: 11.22.33.44

Location office 
IP : 3.3.3.3
DNS : 11.22.33.44

If we do a parial comparison here, we will discover that the difference 
between locations is in the IP's. If he later changes the DNS while he
is
in the office location, wouldnt he be confused that the home location 
changed DNS too ?

Is the current design of the location management taking into account
that there are some settings that are not "locatable", I am thinking
about
the disks-tool & the users-tool. How does the archiver identify what is
locatable or not ? 

regards,
Chema


_______________________________________________
Setup-tool-hackers maillist  -  Setup-tool-hackers@helixcode.com
http://lists.helixcode.com/mailman/listinfo/setup-tool-hackers