Configuring and Managing MPE/iX Internet Services (July 2001)

Chapter 9 189
Apache for MPE/iX
Sample Module Code (mod_hw)
Unsupported Functionality
HP does not support Apache binaries or DSOs built by individuals or
organizations outside of HP.
HP supports the htpasswd and apxs utilities in the /APACHE/PUB/bin
directory but not the other scripts and programs in the bin directory.
Performance
For best performance, files returned to the user should be in bytestream
format. For example; .html, .htm, .shtml, .shtm, .txt, .gif, .jpeg, and .jpg
files should be in bytestream format instead of in the MPE/iX type
format. Bytestream files are more compatible with Apache and with
other POSIX applications than are MPE/iX type files. If a web page
calls many images which are not in bytestream format (BA), the page
will appear to load all the way with all the content visible, yet the
browser will appear hung and the activity icon will keep moving.
If any files under the document root (htdocs), or in other locations that
are storing and accessing web server content, are MPE/iX fixed ASCII
(FA), MPE/iX variable ASCII (VA), or MPE/iX variable binary (VB)
files, consider converting them to bytestream files using the “tobyte”
utility. Program files (fixed binary (FB) files with an NMPROG filecode)
should never be converted.
A file’s filetype can be determined using either the POSIX file command
or the CI listfile command:
shell/iX> file index.html
index.html: commands text
shell/iX> callci listfile ./index.html,2
PATH= /APACHE/PUB/htdocs/
CODE ------------LOGICAL RECORD-------- ----SPACE---- FILENAME
SIZE TYP EOF LIMIT R/B SECTORS #X MX
1B BA 1622 2147483647 1 16 1 * index.html
The index.html file in the previous example is a bytetream file. The
following files are MPE/iX type files:
shell/iX> file index*.html
index.html: MPE/iX 256-byte variable length binary (filecode: 0)
index1.html: MPE/iX 80-byte fixed length ascii (filecode:0)
shell/iX>callci listfile ./index.html,2
PATH= /APACHE/PUB/htdocs/