Forum OpenACS Improvement Proposals (TIPs): TIP #51 (Approved) Require AOLserver 4.x for OpenACS 5.2
This will allow us to use package require and AOL's own support for internationalization rather than the unmaintained code in the OACS extensions.
Making it two releases ahead should give folks sufficient lead time to prepare (moving to 4.x is not difficult)
what in particular isn't ready in SSL support? The run away process problem reported by CR?
I've been running SSL w/ 4.x for a while now w/o problems. Both incoming and outgoing SSL connections.
I don't know if he found a fix or not, I will ask if he doesn't respond to this thread.
We see nsopenssl eating the CPU too - the cause seems to be an infinite
loop in NsOpenSSLConnHandshake. You can see it if you use Netscape/Mozilla
and your domain name doesn't match the certificate. It also seems to
happen when the domain name matches but you close the browser window during
the handshake. (I haven't had the chance to confirm what error that
Scott has been looking into this, and thought that a solution could require
changes to the core because of the aggressive read-ahead in AOLserver 4.x.
As a temporary measure, he is also considering adding a timer to the conn
that would exit the loop if no data has been read over the specified period.
Several folks hosting with me have seen issues...
I got SSL running with it nicely, though not under heavy load.
Be aware that it makes upgrades harder.
Still ... Approved.
That is, if any SSL-related problems are corrected.