HP3000-L Archives

October 1996, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Vance <[log in to unmask]>
Reply To:
Jeff Vance <[log in to unmask]>
Date:
Tue, 8 Oct 1996 17:25:47 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Forwarded from Paul Taffel with his permission:

On Oct 1,  5:37pm, Paul Taffel wrote:
> Subject: Re[4]: Design for System CI vars
>
>   In answer to your questions:
>
>   - Write-only variables MIGHT be useful in the case where one program
>     prompts the user for a password, and later on another program would
>     like to make use of the password without re-prompting, but we don't
>     want anyone walking up to the terminal to be able to :SHOWVAR and see
>     it.  Although I'm sure this wouldn't be as easy as I described, it
>     might be worth further investigation.
>
>   - I suggested HELLO;NEST (or whatever else it's called) as the mechanism
>     for accessing an AIFCHANGELOGON-implemented solution because of the
>     leveraged benefits you'd get 'for free' at the same time: namely
>     truly-isolated processes in the same tree.  Don't forget, as soon as
>     you provide local variables, users will ask for local temp file domains,
>     local file equations, etc.  AIFCHANGELOGON already gives you most of
this.
>     Also, AIFCHANGELOGON implements one set of 'scope rules', do you really
>     want (or need) to introduce another set just for local variables?
>
>   - No problems with you reposting anything here.  Thanks for asking!
>
>   Regards,
>
>   Paul Taffel
>   Quest Software

--

ATOM RSS1 RSS2