On (10/31/08 16:57), Erik Nordmark wrote: > > If the user interface has a '-t' option to specify "transient" then I > think you need to honor it, or generate an error. That limits your > choices. > > If all interface will be persistent across reboots, then it might make > sense to also have all the property settings be persistent. > > The choices depend on which core objects can be transient.
How about the following: - all commands that act on a specific object are always persistently applied to that object. - separate hooks to enable/disable (commit/uncommit?) the object itself for persistent creation - commands that apply globally (to all objects) will support the -t flag Would that be consistent? --Sowmini
