Re: Re: How to create Persistent zval?
Lin Yo-An wrote:
> 3. if so, objects must be serialized to string?
'must' -> 'could' ...
An object consists of a set of software to handle it which is persistent in so
far as it exists in a certain version on the server, and an instance of the data
created for that object ( or an 'array' of them ). Passing that data to later
runs of the code can either be done by producing a 'static' serialization of the
data, or a more flexible approach is store the data in a database. When the
object is recreated it can either be repopulated from the serialization, or from
the data. The first method requires that managing the data is handled directly
by the objects code, while the second allows management from other paths. The
first also introduces restrictions on how modifications can be applied as all
stored serializations would need to be updated, while the second can simply
create additional properties on the fly.
Which method of persistence is used simply depends on other factors, and it's
not uncommon for the serialized data to be stored in a database anyway.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
Thread (14 messages)