View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003463GNUnetcadet servicepublic2014-07-01 11:262018-06-06 22:25
ReporterBart Polot Assigned ToBart Polot Due Date
PriorityhighSeveritytweakReproducibilityN/A
Status closedResolutionwon't fix 
Product VersionGit master 
Target Version0.11.0pre66Fixed in Version0.11.0pre66 
Summary0003463: Tweak "futures" bitfiled for channel ACKs
DescriptionThe "futures" field indicates all messasges received after the one indicated in the "ack" field.

Right now it enumerates messages in direct following order. Bit 0 is ack+1, bit 1 is ack+2 ... bit 63 is ack+64.

Since ack indicates the furthest contiguous message received, ack+1 will NEVER be set, it is implicit in ack that ack+1 is missing.

The futures field should be changed to bit 0 is ack+2 and bit 63 is ack+65.

WARNING: This breaks protocol retro-compatibility.
TagsNo tags attached.

Relationships

related to 0003456 closedBart Polot Cadet's flow control fails in the presence of data loss 

Activities

Bart Polot

2015-05-18 20:17

reporter   ~0009130

ACK+1 will be set if receiving client is slow processing incoming traffic, the receiving service's buffer is full and the sender should slow down.

Issue History

Date ModifiedUsernameFieldChange
2014-07-01 11:26Bart PolotNew Issue
2014-07-01 11:26Bart PolotStatusnew => assigned
2014-07-01 11:26Bart PolotAssigned To => Bart Polot
2014-07-01 11:26Bart PolotRelationship addedrelated to 0003456
2015-03-20 20:44Christian GrothoffPrioritynormal => high
2015-04-30 10:59Bart PolotStatusassigned => acknowledged
2015-05-18 20:17Bart PolotNote Added: 0009130
2015-05-18 20:17Bart PolotStatusacknowledged => resolved
2015-05-18 20:17Bart PolotResolutionopen => won't fix
2015-05-18 20:20Christian GrothoffFixed in Version => 0.11.0pre66
2018-06-06 22:25Christian GrothoffStatusresolved => closed