DDC-946: Evaluate optional use of igbinary for serialization #5476

Closed
doctrinebot opened this Issue Dec 22, 2010 · 4 comments

2 participants

@doctrinebot

Jira issue originally created by user @beberlei:

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

@doctrinebot

Comment created by @ocramius:

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.

@doctrinebot

Issue was closed with resolution "Won't Fix"

@doctrinebot

Comment created by @ocramius:

Just a note. [~beberlei] 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

@Ocramius Ocramius was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot closed this Dec 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment