[Info-vax] Using VMS for a web server

[IanD]

On Thursday, June 4, 2015 at 6:41:42 AM UTC+10, Phillip Helbig (undress to reply) wrote:
> In article <mkno2i$bh$1 at dont-email.me>, David Froble
> <davef at tsoft-inc.com> writes: 
> 
> > Had a short conversation with David Jones some years ago.  Best I can 
> > remember, he said that the OSU web server hadn't been updated for a 
> > while, and from the way he said it, I got the impression there probably 
> > wouldn't be any new work.  Of course, things can always change.
> 
> IIRC he has retired now, and moved the stuff from OSU to source forge.  
> The mailing list seems to have dried up, which surprised me because it 
> is independent of where the software lives.  I can't be bothered to 
> navigate through the SourceForge website, especially because it is not 
> easy with browsers available on VMS.  :-(
> 
> > However, Mark Daniels is adding to WASD, and appears to be available to 
> > look at problems.
> 
> But if he is a single point of (potential) failure, what will happen 
> when he is no longer available?

As opposed to a number of other VMS ports that see one person looking after the whole lot? Python comes to mind here I think

The source code is there if required and a number of folk often delve into it to post issues and Mark fixes them, I'm sure others could take over in a pinch


Getting Apache converted and built on a VMS platform is certainly a more specialised knowledge set than just picking up the source code for WASD which was written for VMS natively and building it

How much VSI would be prepared to assist Mark Daniels is anyone's guess, probably not a lot considering it's not on a lot of systems but that could change if it was bundled with VMS