[Info-vax] Listeners in VMS Basic, was: Re: Integrity iLO Configuration?

Richard Maher maher_rjSPAMLESS at hotmail.com
Thu Jul 1 21:16:59 EDT 2021


On 1/07/2021 10:06 pm, Arne Vajhøj wrote:
> On 7/1/2021 12:18 AM, Richard Maher wrote:
>> On 27/06/2021 2:53 am, Arne Vajhøj wrote:
>>> On 6/25/2021 10:02 PM, Dave Froble wrote:
>>>> I'll just address my opinion of threads.  Not saying they are 
>>>> useless, but, if the OS, VMS, already gives me separate 
>>>> "threads" called processes, why do I want the aggravation of 
>>>> re-inventing it inside my apps?
>>>> 
>>>> I'm sure someone will cry out "performance", but, with today's 
>>>> processors, performance is most likely a rare issue.
>>> 
>>> Threading provides a very convenient programming model.
>>> 
>>> Shared heap is a lot easier than IPC.
>>> 
>>> Sure - it is also possible to shoot oneself in the foot accessing
>>> that shared heap.
>>> 
>>> But for people that understand concurrency problems and locking 
>>> then it should not be a big problem.
> 
>> Yes but a simple single threaded shareable image RTL is much
>> easier than Threading or IPC (Although C# async tasks are pretty
>> easy)
>> 
>> And IIRC correctly there is no thread-granularity
>> T3$PERSONA_ASSUME which allows unprivileged code temporarily assume
>> the Username of the authorized client.
>> 
>> Let VMS check authorization and not try to duplicate it.
> 
> Persona is probably a process attribute not a thread attribute. 
> Process has P0 and S0 space. Threads just have a slice of P1 space.
> 
> But I don't think that is an issue here.

You see no benefit from being able to become the client user so that all 
security checking for files, print submission, dn trigger audit etc is 
done as the user?
> 
> Arne
> 
> 




More information about the Info-vax mailing list