Re: [PHP4BETA] Intended use of session and HTTP_*_VARS.
| From: | Andi Gutmans | Date: | Mon, 06 Mar 2000 19:58:10 +0000 |
| Subject: | Re: [PHP4BETA] Intended use of session and HTTP_*_VARS. | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-11625@lists.php.net to get a copy of this message | ||
Add an .ini setting isn't such a good idea. The more you allow different
installations of PHP to behave differently the harder it will be for
people to share their packages and code with people.
Andi
On Mon, 6 Mar 2000, Shane Burrell wrote:
> On Mon, 06 Mar 2000, Andrei Zmievski wrote:
> > On Mon, 06 Mar 2000, Shane Burrell wrote:
> > > That works great. I have one other question. When global and track vars are
> > > both on the HTTP_STATE_VARS will not update the global counterpart. Its not a
> > > big deal but if it did update the global var it would make easy migration to
> > > the track_vars method only. Thanks again. :)
> >
> > I just disassociated those last week to keep it consistent with other
> > $HTTP_*_VARS[] behaviors. I don't know what to do, some people want it
> > one way, some want it another.
> >
> > -Andrei
> >
>
> We intend to migrate to using only the http_state_vars. Checking things into
> the global scope automatically worked great till our projects got big. Now we
> are faced with migrating to http_state_vars only. After our migration it
> won't be an issue. I may try to re-associate state and global until everything
> uses http_state_vars. I don't know which way it should work but state vars
> are a little different that post or get as far as updating from code. Would it
> make sense to offer a ini setting to control the behavior?
>
>
>