The NetBSD changes didn't make it?
Ian A. Harding
Programmer/Analyst II
Tacoma-Pierce County Health Department
(253) 798-3549
mailto: [EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 05/17/01 05:05PM >>>
AOLserver 3.4 has been released! AOLserver 3.4 is a fully compatible drop-in
replacement for any of the 3.x series. The ChangeLog follows at the bottom
of this message.
Download AOLserver 3.4 today!
ftp://ftp.aolserver.com/server/aolserver-3.4.tar.gz
http://aolserver.com/archive/server/aolserver-3.4.tar.gz
Binaries of AOLserver 3.4 for many platforms are available at:
ftp://ftp.aolserver.com/server/binary/
http://aolserver.com/archive/server/binary
Enjoy!
The AOLserver Team
---cut here---
2001-05-18 Kris Rehberg <[EMAIL PROTECTED]>
*** AOLserver 3.4 RELEASED ***
2001-05-17 Kris Rehberg <[EMAIL PROTECTED]>
* nsd/conn.c: conn is now aware of Latin-1 charsets for ADPs,
requests, query data, and the like in Tcl 8. This does not affect
IS0-8859-1 (see nsd/adp.c below).
(NsTclConnCmd): [ns_conn encoding] reports the encoding used (see
nsd/adp.c below).
* nsd/adp.c: The ADP requests, file parsing, file includes, and
all related ADP functions now force ISO-8859-1 for support of all
Latin-1 character sets in ADPs on nsd8x. There is new handling of
UTF data in Tcl 8 that was implemented in AOLserver 4 which has
been back-ported to support Latin-1 *only* in AOLserver 3.4.
Previously, nsd8x could not handle anything but 7-bit ASCII in
ADPs. The reading of Latin-1 charsets seemed to fail
intermittently in previous 3.x AOLservers. The reason was that
AOLserver reads files in as UTF-8 and some Latin-1 characters
confuse Tcl 8's UTF reader. (Note that the en-us characters in
Unicode, when encoded in UTF-8, look just like 7-bit US ASCII to
computers). Naturally, when non-en-us characters are encountered,
the Tcl 8 UTF-8 reader gets confused. The correct MIME type is
now returned for all Latin-1 charsets. This does not affect
IS0-8859-1.
* thread/pool.c, thread/pthread.cpp, thread/reentrant.c: Tls
entries for memory pools, thread pools, re-entrant libc
replacements, are self-initializing.
* thread/Makefile, tcl8.3.2/unix/Makefile.in: Moved Tcl nsthread
support into Tcl sources.
* tcl8.3.2/generic/tclEvent.c: Fixed library path code as in
AOLserver 4 so Tcl 8 can find encoding files for UTF in a
thread-safe manner.
* nsd/tclstubs.cpp: Back-ported some AOLserver 4 initialization
code. Tls self-initializes. UTF-aware encodings based on file
extension (from AOLserver 4). See nsd/adp.c below.
* nsd/tclinit.c: Tls entry for Tcl interps is self-initializing.
* nsd/nsmain.c: UTF encoding-aware (see nsd/adp.c below).
* nsd/nsd.h: New UTF encoding routines and version strings (see
nsd/adp.c below).
* nsd/dstring.c: NS_DStrings are self-initializing. You should
not need to use Ns_DStringInit anymore, though you still can with
no ill effect.
* nsd/dbinit.c (IncrCount): Tls entry for db handles is
self-initializing.
* nsd/adp.c: Tls entry for ADP parser is self-initializing.
