From: Alex B. <tur...@tu...> - 2001-09-03 22:51:32
|
Hey andi, well, I think in thise case it's unnecessary: If someone wants user variables registered in the user space, they can turn on register_globals (probably using a configuration constant I'll set up) so there's no reason to provide a globalize function. I'd vote for ditching it. I just forwarded a mail I got from PHPClasses called CGI.php which (though I haven't looked at it) seems to have some nice stuff on top of what we have, specifically parsing out "search engine friendly" urls (i.e. no ?moo=foo, /moo/foo/ _a On Mon, 3 Sep 2001, Andreas Aderhold (Thyrell) wrote: > Hi All, > > does anyone make use of globalize feauture in the Request class? I plan to > remove this if noone needs it. > > What it does (if enabled): > > If you get a variable form a HTTP_*_VARS array via the GetVar() method this > variable is referenced to the global namespace. > > i.e.: > > $HTTP_GET_VARS["id"] > $GLOBALS["id"] =& $HTTP_GET_VARS["id"]; > > In my opinion thats completely useless caus it messes up global namespace > and thats what we want to prevent. What do you think? > > Andi > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |