[cap-talk] Save as Reducing the authority of a file browser in a capability OS.

[Rob Meijer]

On Tue, December 29, 2009 05:20, Kevin Reid wrote:
>
> On Dec 28, 2009, at 22:42, Ben Kloosterman wrote:
>
>> The whole SaveAs or "Open With" has always seemed to me to be a poor
>> choice
>> designed entirely to ensure formats are proprietary
>
>
> The relevant aspect of "Save As" in this discussiopn is choosing a new
> filename/location for the document, not choosing the format.
>

What might be interesting questions is, given the parallelisms to OOP,
should 'Safe As':

* Include some sort of private/protected/public flag.
* Allow to choose between the private per pseudo persistent process
  namespace, the 'static' per application+uid namespace, the semi global per
  uid namespace and the global multi user namespace?
* Only create a named reference to a facet/caretaker for the always
  'private' file?


In my view the ideal solution would allow safe-as to create a
facet/caretaker in the static,semi-global or global namespace, defaulting
to a read read only facet /caretaker created in the semi-global namespace.