[DDC-946] Evaluate optional use of igbinary for serialization Created: 22/Dec/10  Updated: 09/Feb/14  Resolved: 07/Feb/14

Status: Resolved
Project: Doctrine 2 - ORM
Component/s: None
Affects Version/s: None
Fix Version/s: None
Security Level: All

Type: Improvement Priority: Major
Reporter: Benjamin Eberlei Assignee: Marco Pivetta
Resolution: Won't Fix Votes: 1
Labels: None


 Description   

Igbinary is supposed to be faster and better than serialize/unserialize(). We should check if its relevant for us (metadata and query caching for example):

https://github.com/phadej/igbinary



 Comments   
Comment by Benjamin Eberlei [ 22/Dec/10 ]

http://ilia.ws/archives/211-Igbinary,-The-great-serializer.html#extended

Comment by Marco Pivetta [ 07/Feb/14 ]

I don't think this is still relevant: closing it, since the serialization improvement can be achieved by hacking a new Doctrine\Common\Cache\Cache implementation for those who really need it.

Comment by Marco Pivetta [ 09/Feb/14 ]

Just a note. Benjamin Eberlei told me that igbinary overrides `unserialize` breaking compat. I personally think that's a very bad idea, but it's not a problem if you use PHP 5.4, since we automatically get rid of the `unserialize` hack and use `ReflectionClass#newInstanceWithoutConstructor()` instead, which is much cleaner

Generated at Tue Sep 30 22:15:55 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.