Re: [AOLSERVER] php + aolserver (is it stable?)
- Original Message - From: "Sean Redmond" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 30, 2002 11:00 AM Subject: Re: [AOLSERVER] php + aolserver (is it stable?) > It works fine almost all the time. I originally had this setup because > we were using the same server (we only had one!) to try out openacs and > to serve webmail, for which we were using SquirrelMail (written in PHP). > Sometimes threads would hang -- it seemed that if users had inboxes with > too many (i.e. thousands) of messages, php would time out, as its > designed to do, but the aolserver thread wouldn't die, and enough hung > threads would hang (but not crash) aolserver. It was nothing too > terrible, so we just set a cron job to periodically restart the server > to clear all the threads out before they got to that critical level. > > When we upgraded to RedHat 6.2 to 7.2, something in the webmail script > that displayed the contents of the inbox consistently crashed aolserver. > I've never been able to track it down, nor have I seen the problem with > anything else. You can look at the bug > (http://bugs.php.net/bug.php?id=14365) if you are interested. > Now we have more servers so we use apache for webmail and aolserver for > everything else (though no PHP except for webmail). > > So I wouldn't recommend it, and there certainly isn't any benefit, but > if you have to use it, it will probably work. Unless it's SquirrelMail > on a RedHat 7.* box -- that definitely will not work! > Or a couple different forum packages.. they do the same thing.. takes AS down hard and fast.. really annoying. I am experimenting with PHP on Aolserver though simply due to the support by DreamWeaver MX via the phrakt extension for easy and rapid development of database applications. -- Patrick Spence www.RandomRamblings.com www.Ariven.com
Re: [AOLSERVER] php + aolserver
Sean,
I tried this again:
./configure --with-aolserver=/usr/local/aolserver \
--with-pgsql=/usr/local/pgsql \
--without-mysql
./make
./make install
no error messages and it still didnt' copy the libphp4.so to my
aolserver folder.
i've added:
ns_section "ns/server/${servername}/module/php"
ns_param map *.php
ns_section "ns/server/${servername}/modules"
ns_param php ${bindir}/libphp4.so
but did not add:
ns_param php_value "session.auto_start 1"
and my main aolserver process is running OACS 4.5, would that conflict
with this?
thanks.
Sean Redmond wrote:
> Edwin,
>
> 'make install' should have put libphp4.so in your aolserver's bin
> directory (e.g. /usr/local/aolserver/bin). Did you add the necessary
> lines to your aolserver config as described in
> {php-src}/sapi/aolserver/README?
>
> Also --with-aolserver-src isn't necessary anymore, so that might have
> confused make. Try reconfiguring without it and rebuilding.
>
>
> Edwin Ho wrote:
>
>> Hi,
>>
>> I'm trying to get php to work with aolserver . I am using
>> "aolserver3.3ad13-oacs1-beta-src.tar.gz" and "php-4.2.2"
>>
>> I configured php like this:
>>
>> ./configure --with-aolserver=/usr/local/aolserver \
>>--with-aolserver-src=/usr/local/src/oacs/aolserver \
>>--with-pgsql=/usr/local/pgsql \
>>--without-mysql
>
--
Regards,
Edwin Ho
Meligent Innovations Inc.
50 - 3195 Granville St.
Vancouver BC, Canada V6H 3K2
T: +1.604.738.8446
F: +1.604.738.8451
http://www.meligent.com
Re: [AOLSERVER] OT: gearing for speed.... (caching connections)
nsopenssl would give you the ability to talk between your servers directly. SSL session caching allows a client and server to set up the initial connection, and then share a long random id. The server uses the id as a key and caches the SSL conn info, such as the keys, ciphers and so on used for the connection. When the client connects again and passes this id. If session caching is turned on in nsopenssl, then the client and server don't have to go throught the whole SSL setup procedure again. The session caching capability is managed by the OpenSSL library internally. BTW, if you're using nsopenssl ALWAYS TURN ON SESSION CACHING. MSIE doesn't work properly without it. /s. > > I have an application where two AOLserver instances on two different > nodes > are going to have lots and lots of communication between themselves -- > I > would prefer to keep the connections transient, but want to know what > the > alternatives are. It's interesting to know that nsopenssl/nsssl may > already > be doing some of this. > > Can you tell me more about how this connection caching is done in > AOLserver? > > Is it handled entirely within nsopenssl/nsssl? Is it actually keeping > the > TCP/IP connection open, or just caching some of the SSL/crypto data? > If the > latter, how does it determine a new request is actually part of an old > SSL > session? > > Thanks, > > > Jerry > -- Scott Goodwin [EMAIL PROTECTED] http://scottg.net
Re: [AOLSERVER] php + aolserver (is it stable?)
Jerry Asher wrote: > Whenever I think about php + aolserver, I am struck by what I've seen in > the past. Comments at the php sites that php + aolserver isn't stable or > ready for production. > > Am I confused about this? > > Also, do php programs embedded within aolserver benefit from: > > A) aolserver's db connection pooling? > B) aolserver's multithreaded model? > C) ??? > > Due to the stability issues, I haven't seen much value in adding php to > aolserver, and not just letting apache and aolserver run side by side with > apache hosting php. > > ??? > > Thanks, > > Jerry It works fine almost all the time. I originally had this setup because we were using the same server (we only had one!) to try out openacs and to serve webmail, for which we were using SquirrelMail (written in PHP). Sometimes threads would hang -- it seemed that if users had inboxes with too many (i.e. thousands) of messages, php would time out, as its designed to do, but the aolserver thread wouldn't die, and enough hung threads would hang (but not crash) aolserver. It was nothing too terrible, so we just set a cron job to periodically restart the server to clear all the threads out before they got to that critical level. When we upgraded to RedHat 6.2 to 7.2, something in the webmail script that displayed the contents of the inbox consistently crashed aolserver. I've never been able to track it down, nor have I seen the problem with anything else. You can look at the bug (http://bugs.php.net/bug.php?id=14365) if you are interested. Now we have more servers so we use apache for webmail and aolserver for everything else (though no PHP except for webmail). So I wouldn't recommend it, and there certainly isn't any benefit, but if you have to use it, it will probably work. Unless it's SquirrelMail on a RedHat 7.* box -- that definitely will not work! -- Sean Redmond BMA Information Systems
Re: [AOLSERVER] php + aolserver (is it stable?)
Whenever I think about php + aolserver, I am struck by what I've seen in the past. Comments at the php sites that php + aolserver isn't stable or ready for production. Am I confused about this? Also, do php programs embedded within aolserver benefit from: A) aolserver's db connection pooling? B) aolserver's multithreaded model? C) ??? Due to the stability issues, I haven't seen much value in adding php to aolserver, and not just letting apache and aolserver run side by side with apache hosting php. ??? Thanks, Jerry
Re: [AOLSERVER] OT: gearing for speed.... (caching connections)
At 05:12 AM 8/30/2002, you wrote: >SSL requires a 7-step handshake between the two systems in order to >establish an SSL connection before any data can be passed. This handshake >also requires multiple cryptographic operations including generation of a >fairly small random number, as well as disk accesses of the digital >certificate files for authentication. SSL session establishment takes a >bit of time. To compensate for this, most SSL implementations will cache >connections between two systems so that what appears to the application >writer as a second session, runs over an existing SSL connection. Even >so, there is some overhead in the encryption once the session has been >established. I have an application where two AOLserver instances on two different nodes are going to have lots and lots of communication between themselves -- I would prefer to keep the connections transient, but want to know what the alternatives are. It's interesting to know that nsopenssl/nsssl may already be doing some of this. Can you tell me more about how this connection caching is done in AOLserver? Is it handled entirely within nsopenssl/nsssl? Is it actually keeping the TCP/IP connection open, or just caching some of the SSL/crypto data? If the latter, how does it determine a new request is actually part of an old SSL session? Thanks, Jerry
Re: [AOLSERVER] php + aolserver
Edwin,
'make install' should have put libphp4.so in your aolserver's bin
directory (e.g. /usr/local/aolserver/bin). Did you add the necessary
lines to your aolserver config as described in
{php-src}/sapi/aolserver/README?
Also --with-aolserver-src isn't necessary anymore, so that might have
confused make. Try reconfiguring without it and rebuilding.
Edwin Ho wrote:
> Hi,
>
> I'm trying to get php to work with aolserver . I am using
> "aolserver3.3ad13-oacs1-beta-src.tar.gz" and "php-4.2.2"
>
> I configured php like this:
>
> ./configure --with-aolserver=/usr/local/aolserver \
>--with-aolserver-src=/usr/local/src/oacs/aolserver \
>--with-pgsql=/usr/local/pgsql \
>--without-mysql
>
> the whole thing went well and I did a 'make install' and that went well
> also.
>
> but the 2 apps don't talk to each other.
>
> Don't I have to put the .so file in aolserver's lib folder? where do I
> get that?
--
Sean Redmond
BMA Information Systems
Re: [AOLSERVER] OT: gearing for speed....
SSL requires a 7-step handshake between the two systems in order to establish an SSL connection before any data can be passed. This handshake also requires multiple cryptographic operations including generation of a fairly small random number, as well as disk accesses of the digital certificate files for authentication. SSL session establishment takes a bit of time. To compensate for this, most SSL implementations will cache connections between two systems so that what appears to the application writer as a second session, runs over an existing SSL connection. Even so, there is some overhead in the encryption once the session has been established. This doesn't mean you should avoid SSL, but you definitely can't expect it to be as fast as a plaintext connection. On Fri, 30 Aug 2002, jerome wrote: > would there be a difference between an http post compared to an https post in > terms of speed? >
Re: [AOLSERVER] OT: gearing for speed....
Yes ;) jerome wrote: >would there be a difference between an http post compared to an https post in >terms of speed? > >. > -- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801 Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
