Could you please clarify:
- Does this proposal affect the user in any way?
- Does it introduce or remove functionality?
- Does it affect compatibility?
As I understand, all the answers are NO, and this is only a refactoring -
correct? Let's make this clear in the IEP
P.S. Separate IEP naming for
Mikhail, as we discussed earlier, Ignite-3 should use it's own counters
since it's a different project.
Better case for me is to use I3EP-XX naming.
Nikolay, +1 to your proposal.
On Thu, Feb 8, 2024 at 6:57 PM Mikhail Pochatkin
wrote:
> Hello, Nikolay.
>
> Thanks for your IEP. I would say that
Hello, Nikolay.
Thanks for your IEP. I would say that IEP-115 already exists in Apache
Ignite 3 section. Looks like current available counter is 119.
чт, 8 февр. 2024 г., 18:27 Николай Ижиков :
> Hello, Igniters.
>
> I want to discuss IEP-115 [1] Binary infrastructure modularization
> Two main
Hello, Igniters.
I want to discuss IEP-115 [1] Binary infrastructure modularization
Two main goal of IEP:
- remove coupling between specific marshaller(BinaryMarshaller) and Ignite core
code.
- simplify Binary code improvements.
- clear SerDes abstraction in core code.
As a result of this IEP
