I'll try to get one going, I'm finishing up a class on C++ that uses
MS VC++ and I might be able to apply that knowledge to the Win32 build
especially when it comes to getting those %*#Q$! extra modules like
nscgi and nsssl built.
For AOLserver 4.x, can anyone please try out building it with the
On 2001.12.18, Kriston Rehberg [EMAIL PROTECTED] wrote:
I'll try to get one going, I'm finishing up a class on C++ that uses
MS VC++ and I might be able to apply that knowledge to the Win32 build
especially when it comes to getting those %*#Q$! extra modules like
nscgi and nsssl built.
Heh.
Was the decision to drop Win32 support on AOLServer 4.0 a political one or a
technical one?
It seems as though there are some demand for Win32 support and as AOLServer
gains momentum, why limit its reach by not supporting Win32 systems? (not
trying to rant)
-Original Message-
From:
Cygwin has limited support for Posix threads. You can check the
Cygwin FAQ at http://cygwin.com/faq/faq.html to see which functions
are missing. Several of the functions that AOLserver 4.x uses aren't
in the DLL yet, making any port at this time difficult.
In response to Dossy's question,
It was a technical one. Making it win32-capable added a lot of code noise
and Jim D. asked the group at one of the chat sessions if there was any
reason not to drop win32 support, at least for 4.x. He wanted to focus on
cleaning up and improving the codebase and not spend a even more time on
Hopefully someone will be able to shed some light on this for me.
I have an aolserver that has been grandfathered down to me and time has
come to renew the ssl cert on the site, however I can't find out how to
generate the cert request.
I found instructions on aolserver.com but they say to run
Hi,
I'm writing a module (in C) that I'd like to do the following when its
routine is called:
- set a long Content-Length header and return the header with some initial
text
- create a worker thread and pass to it the connection information (Ns_Conn)
- return from the routine
- have the worker
+-- On Dec 18, Ramin Naimi said:
- return from the routine
- have the worker thread take over returning the rest of the response to the
browser over the Ns_Conn that was passed to it.
You can't do it. You must not return from your handler until you have
fully handled the HTTP
