Windows — (obsolete) indicate that Interchange is running under Microsoft Windows
The option should be enabled to indicate (an unfortunate) situation where Interchange is running on Microsoft Windows family of products.
However, Unix is best. The Windows version, while perhaps more than just a toy,
is not suitable for high-volume catalog serving. This is mostly due to Windows
NT not fitting the UNIX fork()
model which works so well
with Interchange.
On Microsoft Windows, you will want to stop and re-start your Interchange server at
least once per day. You can use a system agent to automate it — you will
want to stop the server to expire the session database anyway. You need to do
this because Interchange requires the Unix-specific fork()
call
to spawn multi-tasked
servers, and without multi-tasked servers there is a strong possibility of
a memory leak — especially if you use embedded Perl or conditional tags.
Interchange support for Microsoft Windows support has been abandoned. This configuration directive has no purpose; if you think you need it, think twice.