Forum OpenACS Improvement Proposals (TIPs): TIP #51 (Approved) Require AOLserver 4.x for OpenACS 5.2

Collapse
1: TIP #51 (Approved) Require AOLserver 4.x for OpenACS 5.2
Posted by Don Baccus on 02/25/04 06:13 PM
I propose OpenACS 5.1 be the last to officially support AOLserver 3.x+OACS extensions.

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)

Collapse
2: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Tilmann Singer on 02/25/04 06:17 PM
Approve
Collapse
3: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 2)
Posted by Jeff Davis on 02/25/04 06:19 PM
approve.
Collapse
4: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Jon Griffin on 02/25/04 06:49 PM
One caveat, SSL support isn't quite ready.
Collapse
5: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 4)
Posted by Bart Teeuwisse on 02/25/04 07:46 PM
Jon,

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.

/Bart

Collapse
6: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Dave Bauer on 02/25/04 07:47 PM
Approve.
Collapse
7: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Jon Griffin on 02/25/04 08:58 PM
Yes, that is the one.
I don't know if he found a fix or not, I will ask if he doesn't respond to this thread.
Collapse
8: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Peter Marklund on 02/26/04 11:52 AM
approve
Collapse
9: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Cathy Sarisky on 02/27/04 12:49 AM
For folks not following the AOLserver mailing list, here's something from Jamie Rasmussen:

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
triggers.)

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...

Collapse
10: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Malte Sussdorff on 02/27/04 04:11 PM
Approve.

I got SSL running with it nicely, though not under heavy load.

Collapse
11: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Lars Pind on 02/27/04 09:03 PM
Hm.

Be aware that it makes upgrades harder.

Still ... Approved.

That is, if any SSL-related problems are corrected.

/Lars

Collapse
12: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Caroline Meeks on 02/27/04 09:29 PM
Approve
Collapse
13: Re: TIP #51 - require AOLserver 4.x for OpenACS 5.2 (response to 1)
Posted by Don Baccus on 02/28/04 08:54 PM
The SSL problem was with the AOLserver module itself, not AOLserver 4.x per se.  It has been fixed.