You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reduce overall complexity of this component by dropping niche serializers.
Background
As this component is used in a bunch of other components, abandoning it is not as easy as I've thought. Due to this, maintaining this component in the future might be relevant and thus, I'd love to drop support for those serializers which seems to fill a niche such as:
MsgPack
PhpCode
PythonPickle
Wddx
I'd love to focus on IgBinary, Json and PhpSerialize - especially as these are most probably the most popular and mostly used serialization types (just a guess, never used any of those above besides PhpCode which gave me pain due to eval).
Especially wddx seems to not work anymore as you can see by following the commits in #22
Considerations
In case projects are using one of the mentioned serializers above, they might have to integrate the serializers to their projects or switch to one of the still available serializers IgBinary, Json or PhpSerialize.
Due to these changes, other components using this component (such as laminas-cache and all adapters, laminas-hydrator, the doctrine module and a bunch of other components) are unable to use MsgPack, PhpCode, PythonPickle or Wddx.
Proposal(s)
Simply drop the code of these serializers for 4.0 so that the overall maintenance is reduced to the (most probably) mostly used serializers.
Appendix
Especially due to the slight scope of this component (providing two methods via an interface), re-implementing very specific serializers should not be a big deal.
The text was updated successfully, but these errors were encountered:
RFC
Goal
Reduce overall complexity of this component by dropping niche serializers.
Background
As this component is used in a bunch of other components, abandoning it is not as easy as I've thought. Due to this, maintaining this component in the future might be relevant and thus, I'd love to drop support for those serializers which seems to fill a niche such as:
MsgPack
PhpCode
PythonPickle
Wddx
I'd love to focus on
IgBinary
,Json
andPhpSerialize
- especially as these are most probably the most popular and mostly used serialization types (just a guess, never used any of those above besidesPhpCode
which gave me pain due toeval
).Especially
wddx
seems to not work anymore as you can see by following the commits in #22Considerations
In case projects are using one of the mentioned serializers above, they might have to integrate the serializers to their projects or switch to one of the still available serializers
IgBinary
,Json
orPhpSerialize
.Due to these changes, other components using this component (such as
laminas-cache
and all adapters,laminas-hydrator
, the doctrine module and a bunch of other components) are unable to useMsgPack
,PhpCode
,PythonPickle
orWddx
.Proposal(s)
Simply drop the code of these serializers for 4.0 so that the overall maintenance is reduced to the (most probably) mostly used serializers.
Appendix
Especially due to the slight scope of this component (providing two methods via an interface), re-implementing very specific serializers should not be a big deal.
The text was updated successfully, but these errors were encountered: