Re: Call for Votes: JSON location
| From: | Joshua Eichorn | Date: | Fri, 07 Apr 2006 22:50:13 +0000 |
| Subject: | Re: Call for Votes: JSON location | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42136@lists.php.net to get a copy of this message | ||
Pierre wrote:
On 4/8/06, Joshua Eichorn <josh@bluga.net> wrote:I guess that standpoint the code should at least include a json_encode and json_decode even if it provides an OO api as well.I totally fail to see the needs of classes. But yes, it should have the two functions. Because the current code is OO and asking the dev to recode things and break things for all its current users doesn't seem all that nice.
-joshBut it doesn't matter one bit since HTML_AJAX supports more then just JSON so i have it wrapped anyway and detecting the extension and falling back if it doesn't exist is nice and easy in that context even if its not in the quick some JSON out on the page.Excuse me, but we are talking about JSON here, not AJAX. Even it is somehow related/similar, I do not really care about AJAX :-) Anyway, as you said, it is easy for you to use JSON, no matter how. As far as I know im the only user of the code inside of PEAR, i was just giving and example of how there is just one use case, directly outputting JSON where people will care at all what the api looks like.