You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by wr...@locus.apache.org on 2000/06/04 05:49:53 UTC
cvs commit: apache-1.3/htdocs/manual dso.html
wrowe 00/06/03 20:49:52
Modified: htdocs/manual dso.html
Log:
Markup changes to the esteemed Mr. Engelschall's document to inform and
defer discussion of Windows and NetWare within the context of building
dso binaries.
Revision Changes Path
1.16 +8 -0 apache-1.3/htdocs/manual/dso.html
Index: dso.html
===================================================================
RCS file: /home/cvs/apache-1.3/htdocs/manual/dso.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- dso.html 2000/01/18 19:32:40 1.15
+++ dso.html 2000/06/04 03:49:52 1.16
@@ -95,6 +95,13 @@
force the linker to export all global symbols is the main problem one has to
solve when using DSO for extending a program at run-time.
+<P>Windows and NetWare provide similar facilities, although they are
+implemented somewhat differently than the description of Unix DSO throughout
+this document. In particular, DSO modules (DLL's and NLM's, respectively)
+are built quite differently than their Unix cousins. This document does not
+attempt to explore the topic of building DSO modules on these platforms.
+The description of mod_so and it's configuration, however, are similar.
+
<H3>Practical Usage</H3>
<P>The shared library approach is the typical one, because it is what the DSO
@@ -194,6 +201,7 @@
o OpenStep/Mach (4.2)
o DGUX (??)
o NetWare (5.1)
+o Windows (95, 98, NT 4.0, 2000)
</PRE>
<P>