[Info-vax] Programming languages on VMS

[Arne Vajhøj]

On 2/7/2018 2:10 PM, Stephen Hoffman wrote:
> On 2018-02-07 17:56:05 +0000, Arne Vajhj said:
>> On 2/7/2018 12:51 PM, Stephen Hoffman wrote:
>>> Ayup.   Writing out transfers using file versions and file transfers 
>>> might have made quick=hack or simple-design sense a decade or three 
>>> ago and under lower loads and in isolated and always-stable 
>>> configurations with always-stable networks, it's a problematic design 
>>> by present-day standards.  I've seen some entertaining failures of 
>>> these designs under load, too.  Accesses attempted while files or 
>>> directories are still locked during transfers, for instance.  These 
>>> designs don't do well under load.
>>>
>>> It'd be feasible to lock down the file transfers with (preferably) 
>>> asymmetric encryption, but most don't bother with security, or 
>>> there's only enough encryption and authentication sprinkled around 
>>> the app to pass a cursory audit.
>>>
>>> In this era, I'd usually look to enlist a message queue framework, 
>>> and would prefer to avoid bespoke code.   There are framework ports 
>>> available for OpenVMS.
>>
>> HTTP for request/response and message queue for async is widely used.
> 
> Well aware.  I've suggested that in a few implementations.  Used it in 
> various spots, too.

Of course.

>                       OpenVMS lacks a REST framework and the libwww port 
> was problematic when I last looked at it.   A REST framework would be a 
> nice addition to OpenVMS, though.  At a lower — though not necessarily 
> simpler — level, an OpenVMS framework that deals with IPv4 and IPv6, 
> with DNS, and with TLS encryption and authentication would be really handy.

I think you have all that if you are willing to use stuff that start
with J.

:-)

Arne