Project

General

Profile

Task #4464

Make SegmentFetcher pure Signal-based

Added by Muktadir Chowdhury over 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Utils
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:

Description

As per the discussion in #4438-6 and #4438-8, we should make the SegmentFetcher module Signal based. Right now, it is a hybrid of callback and signal that is inconsistent, and reduce readability and maintainability.


Related issues

Blocks ndn-cxx - Feature #4364: Implement congestion control in SegmentFetcherClosed

Actions
Blocks ndn-cxx - Feature #4555: SegmentFetcher: eliminate selector usageClosed

Actions

History

#1

Updated by Davide Pesavento over 2 years ago

  • Category set to Utils
  • Start date deleted (01/15/2018)
#2

Updated by Eric Newberry about 2 years ago

  • Assignee set to Eric Newberry
#3

Updated by Eric Newberry about 2 years ago

  • Status changed from New to In Progress
#4

Updated by Eric Newberry about 2 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 0 to 100
#5

Updated by Junxiao Shi about 2 years ago

  • Blocks Feature #4364: Implement congestion control in SegmentFetcher added
#6

Updated by Eric Newberry about 2 years ago

  • Target version set to v0.7
#7

Updated by Eric Newberry about 2 years ago

  • Status changed from Code review to Closed
#8

Updated by Davide Pesavento about 2 years ago

  • Blocks Feature #4555: SegmentFetcher: eliminate selector usage added
#9

Updated by Junxiao Shi over 1 year ago

20180910 NFD call agreed on the following deprecated feature removal policy:

  • A deprecated feature may be removed 90 days after it was deprecated.
  • A 7-day notice to nfd-dev is required before the removal.

https://gerrit.named-data.net/#/c/ndn-cxx/+/4929/ is removing the deprecated SegmentFetcher::fetch function. There was a concern about whether this Change must wait for a release, or it just needs a 5-day notice as we did in 2014. It has been more than 90 days since the deprecation. Under the policy recorded above, developer needs to send a 7-day notice.

#10

Updated by Davide Pesavento over 1 year ago

Junxiao Shi wrote:

  • A deprecated feature may be removed 90 days after it was deprecated.

I thought Lixia said after 90 days OR the next release, whichever comes first. Did I mishear?

Also available in: Atom PDF