Justtechjobs.com Find a programming school near you






Online Campus Both


php3-list | 199901

RE: [PHP3] db connections, session state From: Brian Leyton (bleyton <email protected>)
Date: 01/22/99

I've been thinking about this as well, since I'm currently on an Openlink
free license that allows only 10 connections (I'll definitely have to buy a
license when we go live - this is just for testing purposes). It seems to
me that if you're using MOD_PHP, and you use persistent connections, then
you would need to restrict Apache to only spawn the number of processes that
you are restricted to.

If you're using non-persistent connections, then the connections would be
closed at the completion of the request, so theoretically, you'd be able to
support more *Apache processes*, though not necessarily more simultaneous
users.

If my thinking is correct, then you might actually be safer with persistent
connections, because you could then allow Apache to spawn a maximum of 25
HTTPDs, and your users would never see an error message that you had
exceeded your quota. Any time you allow more HTTPDs than allowable database
connections, you run the risk of exceeding your quota, and presenting your
user with an error message (though I'd think that you could still safely
allow more than 25 HTTPDs *if* you used non-persistent connections).

Anyone care to comment on the performance implications of these various
options?

Brian

Anyone have any comments on which

> -----Original Message-----
> From: Aaron Gomez [mailto:agomez <email protected>]
> Sent: Friday, January 22, 1999 2:30 PM
> To: 'PHP3'
> Subject: [PHP3] db connections, session state
>
>
>
> I want to use the database extensions that PHP provides. However, my
> understanding is that when a web-client connects, that equates to one
> database connection. Other web-client connections would also equate to
> one database connection. Therefore, if I am using Microsoft SQL server,
> say, for which I am only licensed for 25 connections, how do I provide
> simultaneous connections to a greater number of web-clients exceeding my
> 25 license limit? So, if I have 100 simultaneous web-clients trying to
> get access to my website, how do I accomplish it? Do I have to code
> something special? Better yet, can I maintain an application wide
> database connection for all web-clients? If so how?
>
> Also, how would one maintain session state on the server side for each
> web-client, other than cookies?
>
> Thanks,
>
> Aaron
>
> --
> PHP 3 Mailing List http://www.php.net/
> To unsubscribe send an empty message to php3-unsubscribe <email protected>
> To subscribe to the digest list: php3-digest-subscribe <email protected>
> For help: php3-help <email protected> Archive:
> http://www.php.net/mailsearch.php3
> List administrator:
> zeev-list-admin <email protected>
>
> 

--
PHP 3 Mailing List   http://www.php.net/
To unsubscribe send an empty message to php3-unsubscribe <email protected>
To subscribe to the digest list:  php3-digest-subscribe <email protected>
For help: php3-help <email protected>  Archive:  http://www.php.net/mailsearch.php3
List administrator:  zeev-list-admin <email protected>