Netware, Win32, and OS2 are threaded architectures.
mod_unique_id is ugly, it made several presumptions based on the pid,
which is essentially broken on these other platforms.
If you look at the 2.0 repository, I believe we've gotten around to fixing
these broken assumptions. But Netware, OS2 and Win32 versions 1.3 will essentially
be dead products once 2.0 is released, since the overhaul (for those platforms,
especially) is nearly total. As of 2.0, we all use (essentially) common code,
so we all fly (or crash and burn) together.
Feel free to patch 1.3 based on 2.0 code, but realize it's heavily apr-ized,
so more would need to be done. You have to factor the thread id into the
equation to make it even semi-workable.
Bill
----- Original Message -----
From: "G�nter Knauf" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 8:59 PM
Subject: Apache-1.3: question about mod_unique_id
Hi,
I've compiled mod_unique_id for Win32 and for Netware, and on both platforms it seems
to work the same as with Unix, I can see a
unique id with SSI and cgi scripts; so can someone please explain why we have the
#error about not supporting multitask OS?
Thanks, Guenter.