Skip to content

improve Connectivity Reports Transaction management #311

@SurfingNerd

Description

@SurfingNerd

The Connectivity Report Transactions face different problems.

  • If a Connectivity Report Transaction is invalid, it blocks a Nonce Slot, all further transactions wont get processed because of a Nonce gap.
  • if there is a reconnect, the system stills tries to get through at first a "Disconnect" and then a "Reconnect" Report, in that case the Node should not try to work on reporting.

We should develop a smarter Service Transactions Management, like we did for Parts and ACKS actions.
See commits for reverence:
42e88fa
2d2e044
6c9ce33

Metadata

Metadata

Assignees

Labels

A-Service TransactionsConnected to management and distribution of service transactionsenhancementNew feature or request

Type

No type

Projects

Status

Todo

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions