1. 18 Mar, 2016 2 commits
  2. 17 Mar, 2016 4 commits
  3. 16 Mar, 2016 4 commits
  4. 15 Mar, 2016 2 commits
  5. 14 Mar, 2016 2 commits
  6. 13 Mar, 2016 3 commits
  7. 12 Mar, 2016 1 commit
  8. 11 Mar, 2016 5 commits
  9. 10 Mar, 2016 4 commits
  10. 09 Mar, 2016 1 commit
  11. 08 Mar, 2016 1 commit
    • Mathias Schreiber's avatar
      [TASK] Remove igbinary from cache framework · 582d2e9e
      Mathias Schreiber authored
      The patch removes igbinary serializer support from the cache framework.
      When igbinary support was added back then in PHP 5.3 times, it had the
      potential to serialize data quicker than the default serializer.
      Unfortunately, other promises aren't held:
      * The module found no general acceptance within the PHP community and
        isn't supported very well. PHP 7 is still not officially supported.
      * Last release at the time of this writing was in 2014-08
      * The module must still be compiled from source and no recent
        distribution ever packaged it by default
      * The maintenance load on devOps side is high: The module must be
        recompiled with each minor php release
      * In case the module is not updated, it throws errors at a central place
        of the system and can easily brick a whole instance
      * The module found no huge acceptance by hosters and is only very rarely
        used in real life instances
      * A performance impact is only measurable in very small and highly
        specialized use cases, it typically plays no role in casual frontend
        or backend requests.
      We've seen several life systems in the wild lately with sloppy hosters
      not maintaining the igbinary module within their infrastructure properly.
      The current implementation with VariableFrontend dynamically detecting
      and then force using the module leads to hard crashes in those situations.
      The main issue is that serializing is done via PHPs serializer and
      unserializing using igbinary then fails, effectively rendering the
      entire installation bricked.
      To come by those situations, it is considered more important to deliver
      a stable product than a product that is quicker in more theoretical use
      Thus, the support for this module is kicked from the standard cache
      frontend. In case igbinary still gives significant boost for specialized
      specific instances, an admin can still configure a VariableFrontend that
      uses this serializer.
      Resolves: #74501
      Releases: master
      Change-Id: I8d4407382c941f66e8c2747a82ec4464b95476f8
      Reviewed-on: https://review.typo3.org/47157
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Reviewed-by: default avatarMorton Jonuschat <m.jonuschat@mojocode.de>
      Tested-by: default avatarMorton Jonuschat <m.jonuschat@mojocode.de>
  12. 07 Mar, 2016 1 commit
  13. 06 Mar, 2016 10 commits