Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88457
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <64233ECB-7422-4D7C-A8A5-E77FC98C09E2@gmail.com>
References: <CADbOR2gh6Mbt9Se1E=wvzjApZx8HzqGJi-D4093VCEtUZThjJA@mail.gmail.com>
	<5601F58A.7000602@php.net>
	<CADbOR2jMUYYXTHUMOwRVK4ATW7tEUFgCV5URKkpr2PVc2D+Hxg@mail.gmail.com>
	<64233ECB-7422-4D7C-A8A5-E77FC98C09E2@gmail.com>
Date: Wed, 23 Sep 2015 14:16:39 -0700
Message-ID: <CADbOR2jKn6+Wu2ZdjENrzu700dHnhqPB_=te9R_8aw3diyhccA@mail.gmail.com>
To: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113f3cd467d0ed052070a11f
Subject: Re: [PHP-DEV] Data serialization of objects, want to iterate 'sealed'
 properties then dynamic ones
From: zardozrocks@gmail.com (j adams)

--001a113f3cd467d0ed052070a11f
Content-Type: text/plain; charset=UTF-8

Not my intention to be combative, but what about http://php.net/pcntl_fork
? I've used that before in a robust distributed application that runs
without any intervention for months. It's my understanding that PHP is
thread safe, but not itself multithreaded. I believe there are some
extensions which aren't thread safe. Also correct me if I'm wrong but
Apache 2 should be run in it's prefork mode when using PHP.

Also, any thoughts on my other questions? Sorry if I'm pressing my luck but
they are far more pressing for me currently:
1) Is there not any way to first iterate through the default properties and
then iterate through *only the dynamic properties* ?
zend_object->properties appears to contain ALL properties if the object has
a single dynamically-assigned property.  If so, please advise?  If not, it
sounds like I must iterate through all properties and check each property's
key to see if it's included among the default properties. Please confirm?
2) Will this code ALWAYS return the properties in the same sequence? E.g.,
if I am iterating through N objects of type MyClass, will each instance
iterate the properties in the same order?
3) Will this code ALWAYS iterate over default properties (i.e., "sealed"
properties, those explicitly defined by class definitinos) FIRST and then
iterate any dynamically assigned properties?
These questions are very important for my serialization algorithm.

CODE:


            zobj = zend_objects_get_address(*val TSRMLS_CC);

            if (!zobj->properties) {
                php_printf("***No dynamic properties!\n");
            } else {
                php_printf("***we got dynamic properties...sadly, this will
also iterate through default properties too\n");
                zend_hash_internal_pointer_reset_ex(zobj->properties, &pos);
                while (zend_hash_get_current_data_ex(zobj->properties,
(void **) &value, &pos) == SUCCESS) {
                    if (zend_hash_get_current_key_ex(zobj->properties,
&key, &key_len, &num_index, 0, &pos) == HASH_KEY_IS_STRING) {
                        if (zend_check_property_access(zobj, key, key_len-1
TSRMLS_CC) == SUCCESS) {

                            zend_unmangle_property_name(key, key_len - 1,
&class_name, &prop_name);

                            php_printf("dynamic property is %s, key_len is
%d\n", prop_name, key_len);
                        }
                    }
                    zend_hash_move_forward_ex(zobj->properties, &pos);
                }
            }

On Wed, Sep 23, 2015 at 1:33 PM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> On 23 September 2015 20:48:33 BST, j adams <zardozrocks@gmail.com> wrote:
> >> PHP uses an object store.
> >Am I correct in understanding that the object store is a global data
> >structure? Wouldn't this tend to discourage any attempts at
> >multithreading/multiprocessing within one's PHP script--unless the
> >object
> >store is protected by a lock...
>
> PHP is inherently single-threaded as far as the user is concerned. There
> are many things which would break if you changed that.
>
> The only way I know of to write multi-threaded PHP is using the pthreads
> extension, which comes with some rather large caveats, and uses specific
> objects to communicate between threads.
>
> Regards,
> --
> Rowan Collins
> [IMSoP]
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--001a113f3cd467d0ed052070a11f--