Shmop does just that, it takes a string of data (any data) and puts it in memory. Serialization is something sysvshm extension does.
Ilia Guillaume Ponçon wrote: > It's true. I know shmop, but the ideal would be to be able to store > large persistent variables in memory without serialization operations > (without deserialization with each reading). > > Thanks for these informations. > > Guillaume > > Ilia Alshanetsky wrote: > >> If you just want memory access PHP already offers shmop extension for >> raw data storage and manipulation as well as sysvshm for storing >> serialized variables. >> >> Ilia >> >> Guillaume Ponçon wrote: >> >> >>> Ondrej Ivanič wrote: >>> >>> >>> >>>>> pecl/apc has apc_store/apc_fetch: >>>>> >>>>> http://livedocs.phpdoc.info/index.php?l=en&q=function.apc-store >>>>> >>>> >>>> >>>> I know about APC, but IMHO I can't use it. On webservers are Zend >>>> Optimizer or mmcache (eAccelerator now) used. >>>> >>>> >>> >>> But the approach is very interesting. The french java developpers and a >>> lot of others need these shared memory functions. I think that a >>> displacement in PHP (memory_fetch, memory_store), even with small locks >>> about which Rasmus speaks would be very appreciated ;). >>> >>> >> >> >> >> >> >> > > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
