Opened 7 years ago
Closed 4 years ago
#1046 closed defect (fixed)
Streaming: Optional delay always set
Reported by: | zzz | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 0.9.29 |
Component: | streaming | Version: | 0.9.7.1 |
Keywords: | docs cleanup | Cc: | Zlatin Balevsky |
Parent Tickets: | Sensitive: | no |
Description
Even when 0. See Connection.sendPacket(). Two bytes of overhead per-packet. We should be able to remove it if zero, but check handling on receive side.
Subtickets
Change History (7)
comment:1 Changed 7 years ago by
Cc: | Zlatin Balevsky added |
---|
comment:2 Changed 7 years ago by
Milestone: | 0.9.9 → 0.9.15 |
---|
comment:3 Changed 6 years ago by
Keywords: | docs cleanup added |
---|---|
Milestone: | 0.9.15 |
comment:4 Changed 5 years ago by
Status: | new → open |
---|
comment:5 Changed 4 years ago by
Milestone: | → 0.9.29 |
---|---|
Resolution: | → fixed |
Status: | open → closed |
In 18663f1a4ff03bdcb627a6b2018020c09873ca58 to be 0.9.28-6
comment:6 Changed 4 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
still set in multiple places. will be resolved in #1939
comment:7 Changed 4 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
In bd037c8b542fe0f6125aa16fb3bff5d257b4e955 0.9.28-6
Note: See
TracTickets for help on using
tickets.
An optional delay with a value of zero means 'ack immediately' - see ConnectionPacketHandler?.receivePacket().
Need a more thorough review of the docs and code to see if what we're doing is sensible and consistent.