In a php file I can just include the connection information and reduce the overhead that comes with fopen. Still gives me one central spot for changing connection information as necessary.
There is always more than one way to do it. -Bryan -----Original Message----- From: Dan Joseph [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 11:18 AM To: [EMAIL PROTECTED] Subject: RE: [PHP] Opinion on a method.... Ahh, good thought. I also have it outside the web site directory tree. -Dan Joseph -----Original Message----- From: Bryan Lipscy [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 2:14 PM To: 'Dan Joseph'; [EMAIL PROTECTED] Subject: RE: [PHP] Opinion on a method.... Put the connect info into a php file (i.e. connect.php). If it is ever directly accessed by the client the PHP engine will render a blank page. If your ini file is ever accessed by the client it will render the contents of the ini file. Wonder if removing rwx would adversly affect includes to this php file.......... -----Original Message----- From: Dan Joseph [mailto:[EMAIL PROTECTED] Sent: Friday, April 04, 2003 11:05 AM To: [EMAIL PROTECTED] Subject: [PHP] Opinion on a method.... Hi, I would like to get some opinions here on a method I'm doing to grab connect information for a mysql connection. Currently I am doing: $pinfo = fopen ("/director1/directory2/filename.ini", "r"); I'm looking for a more secure method of doing this. Is XML a solution? Is there something else? Are you doing something similar? All opinions greatly appreciated... -Dan Joseph -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
