(p. 70) (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache API The API directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache 2.0 on Windows NT now uses utf-8 for all filename encodings. These In particular, the Windows version of Apache is now much more efficient, since MPM WINNT can use native networking features in place of the POSIX layer used in Apache 1.3. This benefit also extends to

modules (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache API The directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache 2.0 on Windows NT now uses utf-8 for all filename encodings. These installation. Brian Kernighan's http://www.cs.princeton.edu/~bwk/btl.mirror/ site has a compiled native Win32 binary, http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe which you must save with the

modules (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache API The directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache 2.0 on Windows NT now uses utf-8 for all filename encodings. These installation. Brian Kernighan's http://www.cs.princeton.edu/~bwk/btl.mirror/ site has a compiled native Win32 binary, http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe which you must save with the

modules (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache API The directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache 2.0 on Windows NT now uses utf-8 for all filename encodings. These installation. Brian Kernighan's http://www.cs.princeton.edu/~bwk/btl.mirror/ site has a compiled native Win32 binary, http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe which you must save with the

modules (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache API The directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache 2.0 on Windows NT now uses utf-8 for all filename encodings. These installation. Brian Kernighan's http://www.cs.princeton.edu/~bwk/btl.mirror/ site has a compiled native Win32 binary, http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe which you must save with the

modules (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache API The directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache 2.0 on Windows NT now uses utf-8 for all filename encodings. These installation. Brian Kernighan's http://www.cs.princeton.edu/~bwk/btl.mirror/ site has a compiled native Win32 binary, http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe which you must save with the

(p. 79) (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache httpd API directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache httpd 2.0 on Windows NT now uses utf-8 for all filename encodings particular, the Windows version of the server is now much more efficient, since MPM WINNT can use native networking fea- tures in place of the POSIX layer used in Apache httpd 1.3. This benefit also extends

(p. 79) (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache httpd API directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache httpd 2.0 on Windows NT now uses utf-8 for all filename encodings particular, the Windows version of the server is now much more efficient, since MPM WINNT can use native networking fea- tures in place of the POSIX layer used in Apache httpd 1.3. This benefit also extends

(p. 59) (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache API The API directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache 2.0 on Windows NT now uses utf-8 for all filename encodings. These In particular, the Windows version of Apache is now much more efficient, since MPM WINNT can use native networking features in place of the POSIX layer used in Apache 1.3. This benefit also extends to

(p. 83) (MPMs) and the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the often buggy and poorly performing POSIX-emulation layers. New Apache httpd API directive specifies the server name and port number only for redirection and vhost recognition. Native Windows NT Unicode Support Apache httpd 2.0 on Windows NT now uses utf-8 for all filename encodings particular, the Windows version of the server is now much more efficient, since MPM WINNT can use native networking fea- tures in place of the POSIX layer used in Apache httpd 1.3. This benefit also extends