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
Flyweights are mutable by nature. However, sometimes it is quite handy to make them 'frozen' or immutable.
For this reason, we could be adding a method like copy() like below to the SBE (JAVA) generator template and to agrona's MessageDecoderFlyweight interface:
This is a copy of the decoder and the underlying buffer. To be more in keeping with the SBE design it would makes sense to provide a decoder and buffer as a destination.
We have an upcoming feature to have DTOs created from codecs that may be more appropriate.
To be more in keeping with the SBE design it would makes sense to provide a decoder and buffer as a destination.
.. or have both options available. Assuming such a copy(...) method was exposed by the MessageDecoderFlyweight interface, it would make creating copies on interface level a tad difficult - it would mean new instances would need to be created through reflection, cough, cough.
ad DTO: sounds interesting. Is there an issue for this?
Flyweights are mutable by nature. However, sometimes it is quite handy to make them 'frozen' or immutable.
For this reason, we could be adding a method like
copy()
like below to the SBE (JAVA) generator template and to agrona'sMessageDecoderFlyweight
interface:Volunteering for a PR, if this gets accepted.
The text was updated successfully, but these errors were encountered: