Bug #18236 Updated: EXACT HTTP POST data access

ID: 18236 Updated by: sander@php.net Reported By: foobardotcom@poczta.onet.pl -Status: Open +Status: Bogus Bug Type: Feature/Change Request Operating System: Linux cyberhq 2.4.19-pre6 #2 SMP PHP Version: 4.2.1 New Comment: Please discuss stuff like this on the appropriate mailinglist and not on the bug system. Previous Comments: ------------------------------------------------------------------------ [2002-07-13 07:21:04] foobardotcom@poczta.onet.pl > It is not possible for PHP to magically create Arrays. You mispelled: not "magically", but "logically" :) > It will a) break scripts, because they will not expect > an Array. Hey, did you read this below? > > backwards compatibility alone would justify this > (...) IMO PHPDevTeam should give NEW way to access > variables from request in PHP, that will give "backwards > compatibility" (of course; recent access methods will be > accessible all the time), but with new functionality. I wrote this after taking backwards compatibility into consideration. So, let's give an example: someone who wrote script before, and this script was using $_GET["id"] will have ALWAYS LAST VALUE, like in old parser - and everything will be *exactly* backwards compatibile in this way of accessing values from request. The new-way-parsed query strings will be placed for example in $_G superglobal array. And likewise - make $_POST array deprecated, and bring out new array - for example $_P. Aha! And old method - $_GET should be deprecated like today arrays $HTTP_***_VARS are, so if someone will turn on all errors (error_reporting(E_ALL)), then notices about deprecated calls should be generated. > It will b) break scripts, because some versions of IE > think its better to send all variables 2 times in some > situations. Excuse me, what are You talking about? I didn't heard about anything like this, please, give me some link, example or some information about that issues! But... there are walkarounds for client-side bugs, PHP-programmers can foresee their existence and apply possible the best patches. In spite of fact that the client-side bugs exist, IMO that's not the reason of not-changing PHP in the proper trend. On the other hand, PHPDevTeam shouldn't adapt PHP language to any other (in this case client-side) bugs!!! ------------------------------------------------------------------------ [2002-07-13 05:30:10] sesser@php.net It is not possible for PHP to magically create Arrays. It will a) break scripts, because they will not expect an Array. It will b) break scripts, because some versions of IE think its better to send all variables 2 times in some situations. and btw.... even if your HTTP sends a 404 or whatever reply, it has still to discard the whole posted block. And as long the server has no 10 GBit connection this will be the bottleneck, not the parsing. ------------------------------------------------------------------------ [2002-07-13 03:01:45] foobardotcom@poczta.onet.pl Let's say that's "enough good argument" to change status of this bug to "bogus". This argument tells something about whole PHP team, in fact - about discarding real arguments. I repent of learning PHP... and, as everything seems even Zend Engine 2.0 will not help on fact, that team isn't able to discuss and think... Once again, excuse my english... maybe the last one :-S ------------------------------------------------------------------------ [2002-07-13 02:35:17] sniper@php.net You obviously shouldn't be using PHP.. ------------------------------------------------------------------------ [2002-07-13 02:10:30] foobardotcom@poczta.onet.pl > > the advantage of PHP is exactly that you *don't* have > > to parse query strings or post data yourself > If some feature is *forced* and *auto-off*, that isn't an > advantage. excuse me, I mean "auto-on", not "auto-off"... ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/18236 -- Edit this bug report at http://bugs.php.net/?id=18236&edit=1