Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40910
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.134.187 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:reply-to:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=Dad9BIn95rLUL1TvMMFl9PJU1Ocz6ZP+RffNv/JbeSYTyRUHGAEjDJb/mJsSjEMEq8
         UXix2Lj2nj0IggqsVG/yViAk5ChHkMf3YqR3/u42PE1KeT4lC4Lnd2M7fcdlAVbvaP7J
         ftHnSKMU50eTQDWHVOkSHfQ5M39PA+kyZRavU=
Message-ID: <10845a340810100525y1be28851ta7a88d69ada6359c@mail.gmail.com>
Date: Fri, 10 Oct 2008 13:25:53 +0100
Reply-To: RQuadling@GoogleMail.com
To: "PHP Internals List" <internals@lists.php.net>
In-Reply-To: <48EF41F7.3020400@adplabs.com.br>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <48EDFEED.8080605@adplabs.com.br>
	 <261daaa10810090607h1876200ex1efa43a40cfb24c2@mail.gmail.com>
	 <48EE0387.3040802@adplabs.com.br> <200810091517.37703.et@php.net>
	 <48EE0A34.8020903@adplabs.com.br> <4D.EB.48736.5C97EE84@pb1.pair.com>
	 <48EF41F7.3020400@adplabs.com.br>
Subject: Re: [PHP-DEV] json_encode ignores protected/private class members
From: rquadling@googlemail.com ("Richard Quadling")

2008/10/10 Jarismar Chaves da Silva <jarismar_silva@adplabs.com.br>:
>
>
> Rodrigo Saboya wrote:
>>
>> Jarismar Chaves da Silva wrote:
>>>
>>> I agree with you.
>>> But when using json_encode I believe the developer wants to transfer the
>>> complete object state, just like when using serialize.
>>> Serialize does see private/protected class members, while json_encode
>>> not.
>>> Javascript does not have class-accessors so why not convert
>>> protected/private to public javascript attributes.
>>
>> In theory only the public members are relevant to anyone except the object
>> itself. If you need information about private/protected members you are
>> either using the wrong visibility for your variables or using json for
>> something it's not supposed to do.
>
> Yes, of course. But currently json_encode ignores the attributes even if the
> call is from inside the class.
> <?php
> class Person {
>   protected $name;
>
>   public function __construct($sName) {
>       $this->name = $sName;
>   }
>
>   public function toJSON() {
>       return json_encode($this);
>   }
> }
>
> $person = new Person('jaris');
> print $person->toJSON(); // ==> will print an empty object e.g. {}
> ?>
>
> I don't know if I'm using json_encode for something it's not supposed to do.
> I'm using it to serialize an object to send it to another
> runtime-environment in response to an remote call, just like what I can do
> with SOAP, REST or RMI. In this context I don't see much sense in preventing
> protected/private data from being transfered.
>
> Regards,
> Jaris.
>
>> -- Rodrigo Saboya
>>
>
> --
>
> *Jarismar Chaves da Silva, M.Sc.*
>
> *ADP**Labs** Brazil**
> *jarismar_silva@adplabs.com.br <mailto:jarismar_silva@adplabs.com.br>
> http://www.adp.com
>
>

Let's just for example say that class X has the username and password
values for the login system.

You've made them private as only this class should access them.

How are you going to stop the json_encode() from seeing them and
passing them on.




-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"