Re: [PHP4BETA] Is autoregister of HTTP_STATE_VARS possible?
| From: | Shane Burrell | Date: | Tue, 07 Mar 2000 20:52:37 +0000 |
| Subject: | Re: [PHP4BETA] Is autoregister of HTTP_STATE_VARS possible? | ||
| References: | 1 2 3 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-11718@lists.php.net to get a copy of this message | ||
On Tue, 07 Mar 2000, Andrei Zmievski wrote:
> On Tue, 07 Mar 2000, Shane Burrell wrote:
> > In order to keep our global space clean we have attempted to move to using the
> > HTTP_*_VARS instead of checking them into the global scope. When you disable
> > the global checkin of HTTP_*_VARS it breaks most of our code and most other
> > applications. By leaving global on I disable the ability to migrate
> > successfully to the HTTP_*_VARS approach. I am trying to decide which way is
> > best both for performance and readiblity. I would assume that the HTTP_*_VARS
> > only method is the best way to go but I may be wrong. Before migrating to that
> > method I'd like to know that's the way that is recommended. Here are some
> > examples of things I have tried so far and explanations of what they are.
>
> So, you want everything that's in $HTTP_STATE_VARS[] to be automatically
> registered? What do you mean by 'the global checkin of HTTP_*_VARS'?
>
> -Andrei
> * It's an emergent property of human minds to create. *
If $HTTP_STATE_VARS[] did a session_register for you at least when
register_globals=off and track_vars=on that would make migration easier. In
refering to global checkin I mean register_globals option in the php.ini. Is
using $HTTP_*_VARS with register_globals=off the best way to go?