For my applications, I've been using includes and other file addressing by
using the doc root as the base dir. e.g.
require_once $_SERVER['DOCUMENT_ROOT'] .
'/miniRegDB/includes/miniRegDBconfig.php';
Recently, I ran into a problem with a new installation on a shared host where
the doc root
-Original Message-
From: Al [mailto:n...@ridersite.org]
Sent: Thursday, May 10, 2012 11:44 AM
To: php-general@lists.php.net
Subject: [PHP] Best practice question regarding set_include_path()
For my applications, I've been using includes and other file addressing by
using the doc root
On Thu, May 10, 2012 at 1:50 PM, admin ad...@buskirkgraphics.com wrote:
-Original Message-
From: Al [mailto:n...@ridersite.org]
Sent: Thursday, May 10, 2012 11:44 AM
To: php-general@lists.php.net
Subject: [PHP] Best practice question regarding set_include_path()
For my
On this note - what is considered best practice in a - sent to friend
type thing.
i.e. User inputs their name + message + email + friends email into a
html/flash form
friend gets a link to read the message.
currently I do this:
1 collect form input
2 create hash using the md5/uniqid method :
Hello Guy,
Thursday, December 9, 2004, 12:34:03 PM, you wrote:
GB There's never a security issue here - i.e. i don't mind how many times /
GB who reads the message, but just want to make it hard to just guess keys
GB to read other messages (otherwise it would just be the db id)
GB This method
Guy Bowden wrote:
On this note - what is considered best practice in a - sent to friend
type thing.
i.e. User inputs their name + message + email + friends email into a
html/flash form
friend gets a link to read the message.
currently I do this:
1 collect form input
2 create hash using
-Original Message-
From: Jon Haworth [mailto:[EMAIL PROTECTED]]
Sent: 19 September 2002 18:18
What are peoples' thoughts on one should always return a value from a
function, even if it's always going to be true?
Unprintable!!
There's no point in returning a value if there's no
Hi list,
What are peoples' thoughts on one should always return a value from a
function, even if it's always going to be true?
Cheers
Jon
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
One extra variable to be declared to catch the true (if you do try
and catch it) and one extra line (the return line in the function),
I'd say skip it if you know your never returning anything different.
Adam Voigt
[EMAIL PROTECTED]
On Thu, 2002-09-19 at 13:17, Jon Haworth wrote:
Hi list,
Hi Adam,
What are peoples' thoughts on one should always return
a value from a function, even if it's always going to be
true?
I'd say skip it if you know your never returning anything
different.
Yeah, that's what I was leaning towards :-)
What prompted the question was a
10 matches
Mail list logo
