Project

General

Profile

Actions

Task #1685

closed

Add timeout into FaceStatus dataset

Added by Alex Afanasyev almost 10 years ago. Updated almost 10 years ago.

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

100%

Estimated time:

Description

UDP on-demand faces should have timeouts associated with them. The remaining time of this timeout should be exposed in FaceStatus dataset


Related issues 1 (0 open1 closed)

Blocks NFD - Task #1686: Visualize on demand UDP face timeouts in nfd-statusClosedAlex Afanasyev06/20/2014

Actions
Actions #1

Updated by Alex Afanasyev almost 10 years ago

  • Blocks Task #1686: Visualize on demand UDP face timeouts in nfd-status added
Actions #2

Updated by Alex Afanasyev almost 10 years ago

  • Subject changed from Add timeout into FIB dataset to Add timeout into FaceStatus dataset
  • Description updated (diff)

I'm changing this task, since I forgot that FIB doesn't have concept of timeouts. However, the same "problem" exists with UDP on-demand faces.

Actions #3

Updated by Junxiao Shi almost 10 years ago

ExpirationPeriod field is defined in Face Dataset.

Actions #4

Updated by Junxiao Shi almost 10 years ago

  • Category changed from Tools to Management
  • Start date deleted (06/20/2014)
Actions #5

Updated by Anonymous almost 10 years ago

I'm trying to understand the scope of this change. UdpFace doesn't appear to have any notion of a timeout or expiration time, which prevents the Face Status Publisher from publishing this information (and of course the library needs to be tweaked).

However, UdpChannel does have a notion of "idle face timeout". Is this the expiration time we're talking about here? If so, should this change really be a modification of the Channel Status rather than Face Status dataset?

Actions #6

Updated by Junxiao Shi almost 10 years ago

UdpChannel has idle face timeout. ExpirationPeriod of a UdpFace equals the idle face timeout of its UdpChannel minus the duration it has been idle.

Actions #8

Updated by Alex Afanasyev almost 10 years ago

  • Status changed from New to Resolved
  • Assignee set to Junxiao Shi
  • % Done changed from 0 to 100
Actions #9

Updated by Alex Afanasyev almost 10 years ago

  • Status changed from Resolved to In Progress
  • Assignee changed from Junxiao Shi to Alex Afanasyev
  • % Done changed from 100 to 50
Actions #10

Updated by Alex Afanasyev almost 10 years ago

  • Target version changed from v0.3 to v0.2
Actions #11

Updated by Alex Afanasyev almost 10 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 50 to 100
Actions #12

Updated by Alex Afanasyev almost 10 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF