Requirements

HFRD VMS Hypertext Services ... read this first

| [next] [previous][contents]


4 - Requirements




E ``Out-of-the-box'' the package executes using DEC TCP/IP Services onHboth AXP and VAX platforms. The VMD HTTPd server itself is specificallyLtailored to DEC TCP/IP Services for OpenVMS (v3.3, a.k.a. UCX), particularlyits QIO interface.

; The software was originally written in a VAX C (v3.2) and Blater DEC C (v5.n) environments, under VMS 6.n. No Lconsideration has been given to any other environments. The DEC C run-time Oenvironment is prefered to the VAX C run-time environment because the former's ;greater integrity and improved performance over the latter. 

Executables



I The executables provided with the package have been compiled using DEC C?v5.0 and linked against the VMS v6.2 DECC$SHR.EXE RTL, with the following implications:



G Needless-to-say (but I will anyway), the server requires a privileged ;environment (either account or image) in which to execute. 

Note:

NTo give this software an opportunity to be useful to a larger number of sites NI ported it to TGV MultiNet TCP/IP (v3.4) over New Year 95-96. This has been Otested under VMS VAX 6.2 and seems to work OK. It is basically the DEC TCP/IP NQIO adapted to MultiNet's QIO interface. It is not as exhaustively tested as Lthe DEC TCP/IP version. I have not compiled or tested it using MultiNet on MAXP, we have only the one VAX architecture system using TGV's product, other KVAX and AXP systems use bundled DEC TCP/IP. Just to emphasize once again, MHFRD does not need a MultiNet version, so this is strictly a bonus. I would Nappreciate (but may not end up implementing) any suggestions on improving the networking code.





| [next] [previous][contents]