Re: Transparent task to task

Liste des GroupesRevenir à co vms 
Sujet : Re: Transparent task to task
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.os.vms
Date : 04. Jun 2025, 03:47:48
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <101oc4k$hutu$3@dont-email.me>
References : 1 2 3 4 5
User-Agent : Pan/0.162 (Pokrosvk)
On Tue, 3 Jun 2025 22:20:00 -0400, Arne Vajhøj wrote:

On 6/3/2025 8:26 PM, Lawrence D'Oliveiro wrote:
>
As pointed out already, it’s not the fault of the TYPE command, it’s
the fault of the underlying comms architecture that allows for this
behaviour. It works with any other command that can open an arbitrary
user-specified file through the same API layer (i.e. RMS).
 
Yes.

Furthermore, this is not actually a common thing. It is a unique feature
of VMS that the standard filespec syntax allows for a DECnet node name
plus optional accompanying username and password, so any code that
accesses files through RMS (and who doesn’t?) automatically gets network-
transparent access to remote data this way.

There are a lot of tools in the *nix world that will accept URLs instead
of filename specs, but they have to use some additional layer on top of
stdio in order to get this capability.

Date Sujet#  Auteur
3 Jun 25 * Transparent task to task10Arne Vajhøj
3 Jun 25 +- Re: Transparent task to task1Chris Townley
3 Jun 25 +- Re: Transparent task to task1Lawrence D'Oliveiro
3 Jun 25 +* Re: Transparent task to task2Marc Van Dyck
3 Jun 25 i`- Re: Transparent task to task1Arne Vajhøj
3 Jun 25 `* Re: Transparent task to task5Simon Clubley
3 Jun 25  `* Re: Transparent task to task4Arne Vajhøj
4 Jun 25   `* Re: Transparent task to task3Lawrence D'Oliveiro
4 Jun 25    `* Re: Transparent task to task2Arne Vajhøj
4 Jun 25     `- Re: Transparent task to task1Lawrence D'Oliveiro

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal