[jira] [Updated] (IGNITE-28221) Combining of the message factories.

2026-04-13 Thread Vladimir Steshin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-28221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Steshin updated IGNITE-28221:
--
Fix Version/s: 2.18

> Combining of the message factories.
> ---
>
> Key: IGNITE-28221
> URL: https://issues.apache.org/jira/browse/IGNITE-28221
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
>  Labels: IEP-132, ise
> Fix For: 2.18
>
>  Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> We should consider combing of Discovery message factory and Communication one 
> (and others?).
> Having one message dictionary is simplier.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-28221) Combining of the message factories.

2026-03-27 Thread Anton Vinogradov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-28221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-28221:
--
Description: 
We should consider combing of Discovery message factory and Communication one 
(and others?).

Having one message dictionary is simplier.

  was:
We should consider combing of Discovery message factory and Communication one. 
Having one message dictionary is simplier. And makes simplier sharing, reusing 
of messages and their types ({_}Message#directType(){_}). 

 


> Combining of the message factories.
> ---
>
> Key: IGNITE-28221
> URL: https://issues.apache.org/jira/browse/IGNITE-28221
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Anton Vinogradov
>Priority: Major
>  Labels: IEP-132, ise
>
> We should consider combing of Discovery message factory and Communication one 
> (and others?).
> Having one message dictionary is simplier.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-28221) Combining of the message factories.

2026-03-23 Thread Anton Vinogradov (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-28221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-28221:
--
Description: 
We should consider combing of Discovery message factory and Communication one. 
Having one message dictionary is simplier. And makes simplier sharing, reusing 
of messages and their types ({_}Message#directType(){_}). 

 

  was:
We should consider combing of Discovery message factory and Communication one. 
Having one message dictionary is simplier. And makes simplier sharing, reusing 
of messages and their types ({_}Message#directType(){_}). 

 

Also _Message#directType()_ should be automatically generated relying on 
message type, message name. Probably on its content. Example: 
{_}OptimizedMarshallerUtils#computeSerialVersionUid(){_}.


> Combining of the message factories.
> ---
>
> Key: IGNITE-28221
> URL: https://issues.apache.org/jira/browse/IGNITE-28221
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Anton Vinogradov
>Priority: Major
>  Labels: IEP-132, ise
>
> We should consider combing of Discovery message factory and Communication 
> one. Having one message dictionary is simplier. And makes simplier sharing, 
> reusing of messages and their types ({_}Message#directType(){_}). 
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-28221) Combining of the message factories.

2026-03-12 Thread Vladimir Steshin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-28221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Steshin updated IGNITE-28221:
--
Description: 
We should consider combing of Discovery message factory and Communication one. 
Having one message dictionary is simplier. And makes simplier sharing, reusing 
of messages and their types ({_}Message#directType(){_}). 

 

Also _Message#directType()_ should be automatically generated relying on 
message type, message name. Probably on its content. Example: 
{_}OptimizedMarshallerUtils#computeSerialVersionUid(){_}.

  was:
We should consider combing of Discovery message factory and Communication one. 
Having one message dictionary is simplier. And makes simplier sharing, reusing 
of messages and their types ({_}Message#directType(){_}). 

 

Also _Message#directType()_ should be automatically generated relying on 
message type, message name, propably its content like 
{_}OptimizedMarshallerUtils#computeSerialVersionUid(){_}.


> Combining of the message factories.
> ---
>
> Key: IGNITE-28221
> URL: https://issues.apache.org/jira/browse/IGNITE-28221
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Anton Vinogradov
>Priority: Major
>  Labels: IEP-132, ise
>
> We should consider combing of Discovery message factory and Communication 
> one. Having one message dictionary is simplier. And makes simplier sharing, 
> reusing of messages and their types ({_}Message#directType(){_}). 
>  
> Also _Message#directType()_ should be automatically generated relying on 
> message type, message name. Probably on its content. Example: 
> {_}OptimizedMarshallerUtils#computeSerialVersionUid(){_}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-28221) Combining of the message factories.

2026-03-12 Thread Vladimir Steshin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-28221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Steshin updated IGNITE-28221:
--
Epic Link: IGNITE-25881

> Combining of the message factories.
> ---
>
> Key: IGNITE-28221
> URL: https://issues.apache.org/jira/browse/IGNITE-28221
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Anton Vinogradov
>Priority: Major
>  Labels: IEP-132
>
> We should consider combing of Discovery message factory and Communication 
> one. Having one message dictionary is simplier. And makes simplier sharing, 
> reusing of messages and their types ({_}Message#directType(){_}). 
>  
> Also _Message#directType()_ should be automatically generated relying on 
> message type, message name, propably its content like 
> {_}OptimizedMarshallerUtils#computeSerialVersionUid(){_}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-28221) Combining of the message factories.

2026-03-12 Thread Vladimir Steshin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-28221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Steshin updated IGNITE-28221:
--
Labels: IEP-132 ise  (was: IEP-132)

> Combining of the message factories.
> ---
>
> Key: IGNITE-28221
> URL: https://issues.apache.org/jira/browse/IGNITE-28221
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Anton Vinogradov
>Priority: Major
>  Labels: IEP-132, ise
>
> We should consider combing of Discovery message factory and Communication 
> one. Having one message dictionary is simplier. And makes simplier sharing, 
> reusing of messages and their types ({_}Message#directType(){_}). 
>  
> Also _Message#directType()_ should be automatically generated relying on 
> message type, message name, propably its content like 
> {_}OptimizedMarshallerUtils#computeSerialVersionUid(){_}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-28221) Combining of the message factories.

2026-03-12 Thread Vladimir Steshin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-28221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Steshin updated IGNITE-28221:
--
Ignite Flags:   (was: Docs Required,Release Notes Required)

> Combining of the message factories.
> ---
>
> Key: IGNITE-28221
> URL: https://issues.apache.org/jira/browse/IGNITE-28221
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
>
> We should consider combing of Discovery message factory and Communication 
> one. Having one message dictionary is simplier. And makes simplier sharing, 
> reusing of messages and their types ({_}Message#directType(){_}). 
>  
> Also _Message#directType()_ should be automatically generated relying on 
> message type, message name, propably its content like 
> {_}OptimizedMarshallerUtils#computeSerialVersionUid(){_}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-28221) Combining of the message factories.

2026-03-12 Thread Vladimir Steshin (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-28221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Steshin updated IGNITE-28221:
--
Labels: IEP-132  (was: )

> Combining of the message factories.
> ---
>
> Key: IGNITE-28221
> URL: https://issues.apache.org/jira/browse/IGNITE-28221
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
>  Labels: IEP-132
>
> We should consider combing of Discovery message factory and Communication 
> one. Having one message dictionary is simplier. And makes simplier sharing, 
> reusing of messages and their types ({_}Message#directType(){_}). 
>  
> Also _Message#directType()_ should be automatically generated relying on 
> message type, message name, propably its content like 
> {_}OptimizedMarshallerUtils#computeSerialVersionUid(){_}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)